Summary: | [open type] "Open Type" dialog maxes the CPU while searching | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Karen Butzke <karenfbutzke> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED DUPLICATE | QA Contact: | |
Severity: | major | ||
Priority: | P3 | ||
Version: | 3.3 | ||
Target Milestone: | 3.3 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Karen Butzke
2007-04-06 15:49:13 EDT
Sounds like a duplicate of bug 178551. Can you take a VM snapshot to confirm this assumption (start eclipse using -consoleLog option in line command and hit Ctrl+Break in the MS-DOS window displaying the console)? Thanks I have tried pressing ctrl-break in the dos window and nothing happens. This doesn't look like a deadlock issue to me. I am able to close the type hierarchy dialog, choose the file menu and exit eclipse. This just takes time since eclipse is churning at 99% of my cpu. If I leave eclipse open it never recovers. (In reply to comment #2) > I have tried pressing ctrl-break in the dos window and nothing happens. This > doesn't look like a deadlock issue to me. I am able to close the type > hierarchy dialog, choose the file menu and exit eclipse. This just takes time > since eclipse is churning at 99% of my cpu. If I leave eclipse open it never > recovers. > Bug 178551 summary was not really accurate, it was not a deadlock between threads but an infinite loop in DiskIndex which hits CPU to 100% and cannot be stopped... So, your bug does definitely sound similar... What do you mean by nothing happens? Didn't you see threads dump displayed in the console? If so, are you really sure that you have the -consoleLog parameter in your command line? What JVM are you using? Bug 168726 and bug 167310 are tracking problems with getting the console to work with latest Eclipse builds. The console works for me if I launch Eclipse with: java.exe <vmargs> -jar [..]\plugins\org.eclipse.equinox.launcher_*.jar <eclipseargs> I downloaded the latest I-Build and am unable to repeat the problem. It appears the fix for bug 178551 has fixed this problem *** This bug has been marked as a duplicate of bug 178551 *** Reopen to assign *** This bug has been marked as a duplicate of bug 178551 *** Verified for 3.3M7 for I20070427-0010 |