Bug 243398 - Deadlock on first operation after startup
Summary: Deadlock on first operation after startup
Status: RESOLVED DUPLICATE of bug 244086
Alias: None
Product: Web Tools
Classification: WebTools
Component: Web Standard Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: wst-inbox CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
: 242323 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-07 06:18 EDT by Joe Littlejohn CLA
Modified: 2008-08-25 10:50 EDT (History)
4 users (show)

See Also:

Attachments
Thread dump taken immediately after deadlock occurred (41.30 KB, text/plain)
2008-08-07 06:18 EDT, Joe Littlejohn CLA 		no flags Details
Thread dump taken a few minutes after deadlock occurred (41.31 KB, text/plain)
2008-08-07 06:19 EDT, Joe Littlejohn CLA 		no flags Details
another instance of what looks like the same problem (23.44 KB, text/plain)
2008-08-21 13:16 EDT, David Green 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 Joe Littlejohn CLA 2008-08-07 06:18:44 EDT 
Created attachment 109394 [details]
Thread dump taken immediately after deadlock occurred

Build ID: I20080617-2000

Steps To Reproduce:
1. Open Eclipse, IDE opens and is responsive
 - cursor blinking etc
 - can open Help -> About
 - can switch perspectives
 - can browse projects with Navigator

2. Do almost any operation on a Java project or resource (e.g. close an open java editor, open project properties, etc).

3. Eclipse locks up (GUI is not redrawn), and must be terminated via the Task Manager.

More information:
I've attached two thread dumps. I took a dump when Eclipse deadlocked, then waited for a few minutes and took another one.
Comment 1 Joe Littlejohn CLA 2008-08-07 06:19:24 EDT 
Created attachment 109395 [details]
Thread dump taken a few minutes after deadlock occurred
Comment 2 Jerome Lanneluc CLA 2008-08-18 12:32:32 EDT 
Deadlock is caused by "Worker-3" which is inside a resource change event and thus it holds the lock on the resource tree, but at the same time it is waiting for a dependency graph to be updated: org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.waitForAllUpdates(DependencyGraphImpl.java:431)

Since the resource tree is locked, all operations that try to run an IWorkspaceRunnable are blocked. In particular, I suspect that the operation that is trying to update the dependency graph is running in "Worker-8". This thread is thus locked waiting for the resource tree held by "Worker-3".

Moving to WST.
Comment 3 Jerome Lanneluc CLA 2008-08-19 09:01:21 EDT 
*** Bug 242323 has been marked as a duplicate of this bug. ***
Comment 4 David Green CLA 2008-08-21 13:16:07 EDT 
Created attachment 110596 [details]
another instance of what looks like the same problem
Comment 5 David Green CLA 2008-08-21 13:17:28 EDT 
the workspace where this occurs is unusable -- this problem happens every time it is opened.  In my opinion this should be Critical or Blocker, P2
Comment 6 Jason Sholl CLA 2008-08-25 10:50:21 EDT 

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