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 got following exception when invoking context menu of a java file inside Explorer. I cannnot reproduce it anymore. java.lang.IllegalStateException at org.openide.util.Mutex.leaveImpl(Mutex.java:759) at org.openide.util.Mutex.leave(Mutex.java:742) at org.openide.util.Mutex.leaveImpl(Mutex.java:833) at org.openide.util.Mutex.leave(Mutex.java:742) at org.openide.util.Mutex.readAccess(Mutex.java:272) ... (whole stack trace attached) ----------- NetBeans IDE Dev (Build 200607171800) 1.6.0-rc; Java HotSpot(TM) Server VM 1.6.0-rc-b90 Linux version 2.6.12-1.1390_FC4smp running on i386 en_US (nb); UTF-8
Created attachment 31944 [details] exception stack trace
reassigne to Petr
There was a read transaction with nested postWriteRequest, during processing of the write phase (at read's leave()), the internal data structures has to get corrupted somehow. I don't see anything in the Mutex that could cause this so far.
I'm facing this exception fairly often when working with trunk, say once in two days, on different places/actions.
So you are able to weakly reproduce the problem? Can you try running your IDE with -J-Dorg.openide.util.Mutex.level=500 It will produce a lot of noise on the output, but in case the exception occurs, we could analyze the sequence of actions that led to the problem. Thanks.
I got it again, this time when opening Junit project out of NetBeans sources. I'm attaching messages.log file with the switch mentioned above. It is rather large, the appeared exception resides on line 10642, and its stack trace is little bit different, please check it. ----- NetBeans IDE Dev (Build 200608071800) 1.6.0-rc; Java HotSpot(TM) Server VM 1.6.0-rc-b94 Linux version 2.6.12-1.1390_FC4smp running on i386 en_US (nb); UTF-8
Created attachment 32626 [details] messages.log (compressed)
I'm trying to analyze the log, but it is very hard, as there is no thread info in there. I've improved the logging code in the Mutex, it should shed more light on what's happening with the Mutex. Please try newer build (i.e. build from 12th Oct) with logging turned on and report the log in case you reproduce the failure.
#87932 has better log. *** This issue has been marked as a duplicate of 87932 ***
OK, verified duplicate. Enjoy your log studies ;)