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.
Build: NetBeans IDE Dev (Build 201003290201) VM: Java HotSpot(TM) Client VM, 14.3-b01, Java(TM) SE Runtime Environment, 1.6.0_17-b04 OS: SunOS User Comments: GUEST: i im updating form network zolta: closing IDE ppis: Starting NB. Stacktrace: org.netbeans.core.CLIOptions2$EQStuck: GUI is not responsive at java.lang.Object.wait(Object.java:0) at java.lang.Object.wait(Object.java:485) at java.awt.EventQueue.getNextEvent(EventQueue.java:479) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:236) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
Created attachment 96505 [details] stacktrace
Created attachment 97172 [details] stacktrace Switching IE -> NB.
Created attachment 97286 [details] stacktrace started netbeans
This bug already has 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=165632
Created attachment 97695 [details] stacktrace
Created attachment 100380 [details] stacktrace Opening IDE
Created attachment 101111 [details] stacktrace
Created attachment 101541 [details] stacktrace starting with JDK 6u21 and a form opened. I needed to use this exact update, and I forgot to close the form after closing with u20.
Reporting of EQStuck enabled by fix of issue 179597. Jesse, what do you want to do with these reports now?
Just discard them, I guess. I thought I had already done so, but apparently not. The slowness reporter should produce a report anyway. core-main #2af898699a0f
*** Bug 187491 has been marked as a duplicate of this bug. ***