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.
[200306260100] [jdk 1.4.1_03] Found one Java-level deadlock: ============================= "Debugger operator thread": waiting to lock monitor 0x8087de4 (object 0x449c98c0, a java.awt.Component$AWTTreeLock), which is held by "AWT-EventQueue-0" "AWT-EventQueue-0": waiting to lock monitor 0x8087a2c (object 0x46367360, a org.netbeans.modules.debugger.jpda.JPDADebugger), which is held by "Debugger operator thread"
Created attachment 10805 [details] threads dump
I can repreduce it in my code: I placed breakpoint to my unit test (TestVersin.java:88). I started debugger. The debugger stopped on my breakpoint. After step into the deadlock occured. I can reproduce it only on one line in my code:-( priority increased p2->p1. please evaluate.
Will be fixed to next release. What do you mean by evaluate?!?
Possibly look at the stack trace and decide if the problem is in our debugger and consider if it's likely to happen. And if so, plan fixing the issue, since reproducible deadlock during starting debugger seems as very important issue. Petr, please attach your test code. Thanks.
I'm sorry, I cannot attach my sources. My code uses library with NON SPL licence. I think that this bug is next Q-build showstopper.
Looks like this bug is already fixed in release35 branch, but fix was not propagated to trunk.
Fixed in main trunk.
Diff???
cannot reproduce on build [200307030100] ->verified