Bug 108831

Summary: deadlock while editing java code.
Product: java Reporter: _ pcw <pcw>
Component: SourceAssignee: Jan Lahoda <jlahoda>
Status: RESOLVED DUPLICATE QA Contact: issues <issues.netbeans.org>
Priority: P2 CC: pnejedly, tzezula
Version: 6.x   
Target Milestone: 6.x   
Hardware: Sun   
OS: All   
Whiteboard:
Issue Type: DEFECT Exception Report:
Attachments: thread dump

Description _ pcw 2007-07-04 02:25:30 UTC
See attached stack dump, just locked up w/o warning, had to kill process to get dump.
Comment 1 _ pcw 2007-07-04 02:25:53 UTC
Created attachment 44697 [details]
thread dump
Comment 2 Jan Lahoda 2007-07-09 13:48:49 UTC
Sorry, I do not see any obvious (Java-level) deadlock in the thread dump. Some threads are waiting to lock object
0xd1c24ef0, which is not locked by any thread. AWT (also listed as waiting on 0xd1c24ef0) is even shown as RUNNABLE. If
it happens again, please try to get the thread dump using jstack with the "-m" parameter. Thanks.
Comment 3 Petr Nejedly 2007-07-23 13:01:29 UTC
Note that it can be a livelock and the thread dump was caught just after another cycle of unlocking 0xd1c24ef0, ot there
might be a heap space shortage which would slow down everything a lot.
Comment 4 Tomas Zezula 2007-09-20 08:21:46 UTC

*** This issue has been marked as a duplicate of 110074 ***
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