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.
AWT Event Dispatch thread is blockend on an Object.wait() call. I would recommend uwing wait(long) in a loop and using some synced block to verify that it should exit the wait or re-wait. This happens a bit too often
Created attachment 28817 [details] ctrl-break stack trace of locked threads
AntProjectChildren.refreshKeys tries to take the mutex and is waiting for someone to drop it? The one holding it is the JavaEditor thread? Or the Hints thread? Putting Mila and Honza on CC. Any idea?
Nothing is wrong with Mutex, it behaves exactly as designed and as expected. There might be something wrong with ExclusiveMutex or one of its users and no smartness in Mutex would prevent it w/o breaking Mutex contract (i.e. breaking the lock). Yes, JavaEditor holds the Children.MUTEX and tries to acquire javamodel transaction lock (ExclusiveMutex), which is held by? Who knows, but I have seen several instances of staled ExclusiveMutex w/o any holder before. Reassigning to javacore.
Javacore module was replaced by Retouche infrastructure. This bug is not valid in trunk any more.
Reorganization of java component