Bug 120138 - typing period after enumeration element tacks cpu for 30+ secs.
Summary: typing period after enumeration element tacks cpu for 30+ secs.
Status: RESOLVED DUPLICATE of bug 107580
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-09 12:43 EST by Ray Case CLA
Modified: 2005-12-13 10:48 EST (History)
0 users

See Also:


Attachments
eclipse 3.0.1M6 .log file (5.81 KB, text/plain)
2005-12-13 00:10 EST, Ray Case CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ray Case CLA 2005-12-09 12:43:10 EST
public class ReportBackWrapper
{

    public enum ReportbackType
    {
        DiagnosticReport(4),
        PurchaseReport(6),
        ADRM(10).<-- typing this period here (typo) will tack the cpu for too long... 
    }

}

please note that this is with myeclipse installed OVER eclipse 3.1.1

Thanks for your time and efforts!
Ray Case
Comment 1 Ray Case CLA 2005-12-09 12:47:23 EST
build: M20050929-0840
Comment 2 Ray Case CLA 2005-12-11 14:58:46 EST
I am upgrading the severity of this bug to 'major' because after this happens, the IDE goes into a limbo state - you can not save the file that the error has occured in. You get an alert window that says 'save Failed:null'  

This also happens in base Eclipse 3.1.0, so MyEclipse has nothing to do with it.

Thanks,
Ray
Comment 3 Olivier Thomann CLA 2005-12-11 16:32:55 EST
Could you please provide your .log file?
Thanks.
Comment 4 Olivier Thomann CLA 2005-12-12 18:43:12 EST
David, could this be a duplicate of bug 107580?
Comment 5 Ray Case CLA 2005-12-13 00:10:41 EST
Created attachment 31612 [details]
eclipse 3.0.1M6 .log file

Actually, this .log entry is very telling.  Its says 'java.version=1.4.1_02' -
obviously 'enum' is not going to work.  With JDK 5.0.06 It still stalls the JDK for a bit, but it doesn't die.

I thought I did a thorough job searching the bug directory.  Obviously, I didn't. My dialup connection at home doesn't help.  I am sorry.
Comment 6 David Audel CLA 2005-12-13 10:48:42 EST

*** This bug has been marked as a duplicate of 107580 ***