This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 32252 - Deadlock on startup
Summary: Deadlock on startup
Status: CLOSED DUPLICATE of bug 30950
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P2 blocker (vote)
Assignee: issues@projects
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2003-03-24 19:34 UTC by David Weatherford
Modified: 2004-04-19 16:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (12.27 KB, text/plain)
2003-03-24 19:35 UTC, David Weatherford 		Details
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 David Weatherford 2003-03-24 19:34:23 UTC 
I often get a deadlock when the IDE is starting
up.  The
"AWT-EventQueue-0" thread is initializing the java
editor and makes
a call to ProxyLookup.lookup() which calls into
the projects
subsystem.  While holding a lock on

  org.netbeans.api.projects.ProjectMemberList.LOCK

it then kicks off an
o.n.loaders.FolderList.getChildren task
waits for it.  The "Folder recognizer" task calls into
the projects subsystem to do a getProjectMember(),
which tries
to lock the same string.

See attached thread dump.
Comment 1 David Weatherford 2003-03-24 19:35:13 UTC 
Created attachment 9507 [details]
thread dump
Comment 2 Dusan Balek 2003-07-23 16:04:41 UTC 
Studying attached thread dump, this deadlock seems to be the same as
in #30950.

*** This issue has been marked as a duplicate of 30950 ***
Comment 3 Jan Becicka 2003-11-25 13:59:35 UTC 
As described in
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the
current work on projects prototype has been stopped.

Marking issue as VERIFIED --->
Comment 4 Jan Becicka 2003-11-25 14:08:24 UTC 
---> CLOSED