Bug 361235 - 100% CPU usage when Starting Eclipse with Initialize Java Tooling and Refreshing Workspace: Apparent Deadlock But Not?
Summary: 100% CPU usage when Starting Eclipse with Initialize Java Tooling and Refresh...
Status: VERIFIED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.8 M3   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 06:51 EDT by Joshua Chaitin-Pollak CLA
Modified: 2011-10-24 00:42 EDT (History)
4 users (show)

See Also:

Attachments
Thread dump from jvisualvm (27.12 KB, text/plain)
2011-10-18 06:52 EDT, Joshua Chaitin-Pollak CLA 		no flags Details
Secondary Threaddump (26.19 KB, text/plain)
2011-10-18 07:06 EDT, Joshua Chaitin-Pollak CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Chaitin-Pollak CLA 2011-10-18 06:51:11 EDT 
Build Identifier: 20110916-0149

When I start Eclipse, it has started to consume 100% CPU. The Progress view shows "Refreshing workspace" and "Initializing Java Tooling", neither are making progress.

Reproducible: Always

Steps to Reproduce:
1. I have multiple Java projects in my workspace. They all use the Maven plugin and I also have the Accurev plugin configured, although I am not logged in.
Comment 1 Joshua Chaitin-Pollak CLA 2011-10-18 06:52:51 EDT 
Created attachment 205410 [details]
Thread dump from jvisualvm
Comment 2 Joshua Chaitin-Pollak CLA 2011-10-18 06:55:14 EDT 
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.
Comment 3 Joshua Chaitin-Pollak CLA 2011-10-18 07:06:51 EDT 
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.
Comment 4 Satyam Kandula CLA 2011-10-18 07:12:45 EDT 
I see Accurev in the callstack. Can you try without Accurev plugin?
Comment 5 Joshua Chaitin-Pollak CLA 2011-10-18 07:27:32 EDT 
(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.
Comment 6 Ayushman Jain CLA 2011-10-18 08:02:36 EDT 
(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.
Comment 7 Joshua Chaitin-Pollak CLA 2011-10-18 08:29:51 EDT 
I am ok with that. Sorry for the disturbance. Is there anything Eclipse can do about poorly behaved plugins?
Comment 8 Remy Suen CLA 2011-10-18 08:52:41 EDT 
(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.
Comment 9 Ayushman Jain CLA 2011-10-18 09:19:41 EDT 
Thanks Remy. Closing as NOT_ECLIPSE.
Comment 10 Srikanth Sankaran CLA 2011-10-24 00:42:51 EDT 
Verified for 3.8 M3