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 150779 - Additional lock checks
Summary: Additional lock checks
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-20 21:53 UTC by _ tboudreau
Modified: 2016-07-07 08:39 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 _ tboudreau 2008-10-20 21:53:12 UTC 
I notice we have a test that throws an exception if Children.MUTEX is entered while in ProjectManager.MUTEX.

This sort of test is a good thing.  I wonder if it would be worthwhile also to test Thread.holdsLock
(someComponent.getTreeLock()), since this is a potent source of deadlocks (possibly also in Children.MUTEX?)

getTreeLock() returns a static Object; the method is not static but it would be simple to create a component and hold
the resulting value.
Comment 1 Antonin Nebuzelsky 2010-03-29 14:10:52 UTC 
Change of default owner.
Comment 2 Martin Balin 2016-07-07 08:39:20 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss