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: | RunUserAction called on AWT-Event-Queue | ||
---|---|---|---|
Product: | contrib | Reporter: | sreimers <sreimers> |
Component: | JMX | Assignee: | Jean-francois Denise <jfdenise> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | blocker | CC: | tzezula, vstejskal |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Stacktrace of lock up |
Description
sreimers
2009-03-17 19:01:30 UTC
Created attachment 78322 [details]
Stacktrace of lock up
Please generate full threaddump (http://wiki.netbeans.org/GenerateThreadDump) when the IDE is frozen and attach it here. The stacktrace you attached shows only one thread (AWT), which is not enough to diagnose the deadlock. Thanks Unfortunately there is just a part of the deadlock. It's impossible to say who is the second participant. Probably some invokeAndWait() or Children.MUTEX. |