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 editing java code. | ||
---|---|---|---|
Product: | java | Reporter: | _ pcw <pcw> |
Component: | Source | Assignee: | Jan Lahoda <jlahoda> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | pnejedly, tzezula |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | thread dump |
Description
_ pcw
2007-07-04 02:25:30 UTC
Created attachment 44697 [details]
thread dump
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. 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. *** This issue has been marked as a duplicate of 110074 *** |