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.
Summary: | deadlock while running gdb | ||
---|---|---|---|
Product: | platform | Reporter: | tbrunhoff <tbrunhoff> |
Component: | JDK Problems | Assignee: | issues@platform <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | issues, jglick |
Priority: | P1 | Keywords: | THREAD |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | stack-2009-02-03.1.txt |
Description
tbrunhoff
2009-02-04 02:49:10 UTC
Created attachment 76526 [details]
stack-2009-02-03.1.txt
Product Version = NetBeans IDE Dev (Build 200812180001) Operating System = Linux version 2.6.22.19 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 dir 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. |