Bug 44052 - Deadlock on startup
Summary: Deadlock on startup
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 critical (vote)
Target Milestone: 3.0 M4   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-02 03:42 EDT by Andre Weinand CLA
Modified: 2003-10-14 11:54 EDT (History)
2 users (show)

See Also:

Attachments
full thread dump (10.77 KB, text/plain)
2003-10-02 03:43 EDT, Andre Weinand 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 Andre Weinand CLA 2003-10-02 03:42:11 EDT 
I20030930
started Eclipse this morning: deadlock (see attachment)
Comment 1 Andre Weinand CLA 2003-10-02 03:43:07 EDT 
Created attachment 6304 [details]
full thread dump
Comment 2 John Arthorne CLA 2003-10-02 11:56:20 EDT 
In main the DeltaProcessingState object is locked, and it is attempting to lock
the workspace.

In Worker-0 the workspace is locked for notification, and the listener is trying
to acquire the DeltaProcessingState object.

Philippe, this looks a JDT regression?
Comment 3 Philipe Mulet CLA 2003-10-02 12:49:09 EDT 
Seems our bug, we shouldn't perform a runnable inside our private lock... we 
had similar issue when populating the model.
Comment 4 Philipe Mulet CLA 2003-10-02 17:11:02 EDT 
Fixed. CP initializers are now running outside our lock
Comment 5 Philipe Mulet CLA 2003-10-02 17:11:56 EDT 
Fixed.
Comment 6 David Audel CLA 2003-10-14 11:54:11 EDT 
Verified.