After running a (long) c++ app for a couple of minutes, it hit a break point. I left it at that breakpoint and poked
around off and on for about two hours. During the final session of poking, the ide locked up. The attached jstack
output shows a deadlock. If there is some tool I can use to get more info, I'll leave the ide the way it is until
perhaps tomorrow mid morning (4 Feb 2009 10am PST).
Created attachment 76526 [details]
Product Version = NetBeans IDE Dev (Build 200812180001)
Operating System = Linux version 18.104.22.168 running on amd64
Java; VM; Vendor = 1.7.0-ea; Java HotSpot(TM) 64-Bit Server VM 13.0-b01; Sun Microsystems Inc.
Runtime = Java(TM) SE Runtime Environment 1.7.0-ea-b27
Java Home = /usr/java/jdk1.7.0/jre
System Locale; Encoding = en_US (nb); UTF-8
dead lock in org.netbeans.core.windows.view.ui.MainWindow
project guys, please evaluate:
> - locked <0x00002aaabbccb220> (a org.netbeans.core.windows.view.ui.MainWindow)
> at org.netbeans.modules.project.ui.Hacks$1$1.run(Hacks.java:130)
I don't think that NetBeans code is the guilty in this deadlock. Jesse, please could you verify that. Thanks.
It would look to be a bug in AWT - various Frame methods synchronize on Frame.this rather than using the AWT lock.
I don't think the project system is involved. It just calls Frame.setTitle on the AWT thread.
looks like jdk bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6774156
OK. Be sure to put 'netbeans' in the keyword field and best to mention this bug report in a comment.