Bug 157876 - deadlock while running gdb
deadlock while running gdb
Status: RESOLVED WONTFIX
Product: platform
Classification: Unclassified
Component: JDK Problems
6.x
PC Linux
: P1 (vote)
: TBD
Assigned To: issues@platform
issues@platform
jdk_bug_6774156
: THREAD
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-04 02:49 UTC by tbrunhoff
Modified: 2009-02-19 22:53 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
:


Attachments
stack-2009-02-03.1.txt (22.02 KB, text/plain)
2009-02-04 02:49 UTC, tbrunhoff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tbrunhoff 2009-02-04 02:49:10 UTC
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).
Comment 1 tbrunhoff 2009-02-04 02:49:57 UTC
Created attachment 76526 [details]
stack-2009-02-03.1.txt
Comment 2 tbrunhoff 2009-02-04 02:54:24 UTC
  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
Comment 3 Alexander Simon 2009-02-04 07:02:01 UTC
dead lock in org.netbeans.core.windows.view.ui.MainWindow
Comment 4 Stanislav Aubrecht 2009-02-04 10:08:57 UTC
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)

Comment 5 Milan Kubec 2009-02-04 13:47:12 UTC
I don't think that NetBeans code is the guilty in this deadlock. Jesse, please could you verify that. Thanks.
Comment 6 Jesse Glick 2009-02-11 01:56:24 UTC
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.
Comment 7 Stanislav Aubrecht 2009-02-11 08:18:03 UTC
looks like jdk bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6774156
Comment 8 Jesse Glick 2009-02-11 15:36:59 UTC
OK. Be sure to put 'netbeans' in the keyword field and best to mention this bug report in a comment.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo