Summary: | 100% CPU usage when Starting Eclipse with Initialize Java Tooling and Refreshing Workspace: Apparent Deadlock But Not? | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Joshua Chaitin-Pollak <josh> | ||||||
Component: | Core | Assignee: | Ayushman Jain <amj87.iitr> | ||||||
Status: | VERIFIED NOT_ECLIPSE | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | amj87.iitr, remy.suen, satyam.kandula, srikanth_sankaran | ||||||
Version: | 3.8 | ||||||||
Target Milestone: | 3.8 M3 | ||||||||
Hardware: | Macintosh | ||||||||
OS: | Mac OS X - Carbon (unsup.) | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Joshua Chaitin-Pollak
2011-10-18 06:51:11 EDT
Created attachment 205410 [details]
Thread dump from jvisualvm
I left Eclipse running for 10-15 minutes, and the blockage seems to have cleared. I lowered the importance of the bug because of this. However I think it is still a problem, because at first glance it appears Eclipse is completely locked up and unusable for around 10 minutes. There is no UI feedback than any progress is being made. Created attachment 205411 [details]
Secondary Threaddump
Eclipse locked up (again) soon after I updated the bug saying that it wasn't locked up. Go figure.
Now I have a modal dialog box on screen that says "Progress Information" and "Operation in progress...". Clicking cancel does nothing. Eclipse is using 120% of the CPU.
Here is the current thread dump.
I see Accurev in the callstack. Can you try without Accurev plugin? (In reply to comment #4) > I see Accurev in the callstack. Can you try without Accurev plugin? Eclipse seems much more compliant without accurev installed. (In reply to comment #5) > Eclipse seems much more compliant without accurev installed. In that case, the issue must be reported to Accurev. I intend to close as NOT_ECLIPSE. I am ok with that. Sorry for the disturbance. Is there anything Eclipse can do about poorly behaved plugins? (In reply to comment #7) > Is there anything Eclipse can do > about poorly behaved plugins? Generally no. Not unless we have sufficient information about the problem in question. Thanks Remy. Closing as NOT_ECLIPSE. Verified for 3.8 M3 |