329974 – Eclipse doesn't start up. Just produces a high cpu load.

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329974 - Eclipse doesn't start up. Just produces a high cpu load.

Summary: Eclipse doesn't start up. Just produces a high cpu load.

Status:	RESOLVED DUPLICATE of bug 327801

Alias:	None

Product:	WTP Java EE Tools
Classification:	WebTools
Component:	jst.j2ee (show other bugs)
Version:	3.2
Hardware:	PC Windows XP

Importance:	P3 critical (vote)
Target Milestone:	3.2.3
Assignee:	Jason Sholl
QA Contact:	Chuck Bridgham

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-11-11 04:03 EST by Jochen Stiepel
Modified:	2010-11-16 09:27 EST (History)
CC List:	3 users (show)

See Also:

Attachments
Threadump from visualvm (41.88 KB, text/plain) 2010-11-11 04:13 EST, Jochen Stiepel	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 Jochen Stiepel

2010-11-11 04:03:01 EST

Build Identifier: M20100909-0800

Java 1.6.22
M2Eclipse 0.12.0 
Subclipse 1.6.15, Subversion 1.6.13

Eclipse startup stop's after "Loading Workspace". Eclipse just produces a high cpu load (2 CPU's - 70%, both CPU's are used).

It happened already 3 times. The only known workaround is, to delete files inside: workspace\.metadata\.plugins\org.eclipse.core.resources\ (.snap, .safetable, root\.markers.snap, root\.indexes); and restart. Now all projects are lost, and import them again.

It seams that there is a deadlock during startup.

Reproducible: Sometimes

Steps to Reproduce:
1. Start Eclipse
2. Sometimes it hangs, not always.

Comment 1 Jochen Stiepel

2010-11-11 04:13:12 EST

Created attachment 182886 [details]
Threadump from visualvm

Comment 2 Jay Arthanareeswaran

2010-11-11 04:37:11 EST

The containers seem to be attempting the resource locks. Moving to Web tools for investigation.

Comment 3 Carl Anderson

2010-11-11 13:50:19 EST

I believe this is the same DependencyGraph deadlock - assigning to Jason.

Comment 4 Jason Sholl

2010-11-16 09:27:12 EST

This is already fixed in the latest 3.2.3 drivers.

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