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.
I encountered a "deadlock" during NetBeans startup. The strange thing is that the CPU usage was at 100% (and not near 0% which is typical for deadlocks). I had a build made from NetBeans sources updated on 6 April at about 3:00 PM CEST (1:00 PM GMT). I am attaching a full thread-dump.
Created attachment 14311 [details] thread-dump
probably problem in JVM (wating on condition)
I won't blame JVM so fast. waiting on condition is there because of allocation. JVM was probably doing GC just before the thread dump was taken. If CPU is 100% then it's not a deadlock. It may be some infinite loop keeping the threads around busy or some kind of livelock (e.g. two threads pinging each other). I'd need more dumps few seconds apart, every time CPU is 100% Anyway, I have strong indication that this is our long-lasting livelock in Mutex, which is finally easy to reproduce (I've just reproduced it) thanks to few buildsystem aspects: 1. It remembers all opened nodes in the projects view 2. It computes the package view by touching _all_ the data objects 3. You had several nodes opened before shutdown This together stresses Mutex enough to livelock.
OK, tkis is actually a dup of #33398, but one that will finally help us to solve that long standing problem. Thanks much for the report. *** This issue has been marked as a duplicate of 33398 ***
closed