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.

Bug 160494 - RunUserAction called on AWT-Event-Queue
Summary: RunUserAction called on AWT-Event-Queue
Status: RESOLVED INCOMPLETE
Alias: None
Product: contrib
Classification: Unclassified
Component: JMX (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jean-francois Denise
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-17 19:01 UTC by sreimers
Modified: 2009-03-24 18:25 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stacktrace of lock up (4.40 KB, text/plain)
2009-03-17 19:03 UTC, sreimers 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sreimers 2009-03-17 19:01:30 UTC 
This locks up my NetBeans
Comment 1 sreimers 2009-03-17 19:03:08 UTC 
Created attachment 78322 [details]
Stacktrace of lock up
Comment 2 Vitezslav Stejskal 2009-03-24 11:20:09 UTC 
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
Comment 3 Tomas Zezula 2009-03-24 18:24:21 UTC 
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.