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 224655 - "java.lang.AssertionError: Must not wait in AWT here" on startup of 7.3 Nightly Build 201301090001
Summary: "java.lang.AssertionError: Must not wait in AWT here" on startup of 7.3 Night...
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Logger (show other bugs)
Version: 7.3
Hardware: PC Windows Vista
: P1 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-09 14:44 UTC by tnleeuw
Modified: 2013-01-17 14:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NetBeans logfile produced by current nightly builds, containing nothing but exceptions already pasted in main body of report. (971.93 KB, application/octet-stream)
2013-01-09 14:44 UTC, tnleeuw 		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 tnleeuw 2013-01-09 14:44:15 UTC 
Created attachment 130044 [details]
NetBeans logfile produced by current nightly builds, containing nothing but exceptions already pasted in main body of report.

For the last several days the Nightly Builds are throwing me this error on startup; repeatedly. Until after several exceptions it just seems to hang totally and I have to kill the NB process.

I don't know when this started since I didn't download any nightly since 20-Dec-2012 (XMas break) until 6-Jan-2013.

Since then the nightlies of 6-Jan-2013 up to 9-Jan-2013 fail to start and the process eventually has to be killed.

I do get a dialog to report the error but never got an email to confirm that this succeeded, also I'm not usually able to enter any comments b/c the textfield doesn't get focus.


The exception is:

java.lang.AssertionError: Must not wait in AWT here
	at org.netbeans.modules.uihandler.UIHandler.waitFlushed(UIHandler.java:204)
	at org.netbeans.modules.uihandler.UIHandler.waitFlushed(UIHandler.java:199)
	at org.netbeans.modules.uihandler.Installer.getLogsSize(Installer.java:695)
	at org.netbeans.modules.uihandler.api.Controller.getLogRecordsCount(Controller.java:80)
	at org.netbeans.modules.uihandler.interactive.SubmitStatus$NrLabel.adjustSize(SubmitStatus.java:131)
	at org.netbeans.modules.uihandler.interactive.SubmitStatus$NrLabel.run(SubmitStatus.java:119)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:666)
	at java.awt.EventQueue.access$400(EventQueue.java:81)
	at java.awt.EventQueue$2.run(EventQueue.java:627)
	at java.awt.EventQueue$2.run(EventQueue.java:625)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:636)
	at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
[catch] at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)


....

And eventually:

SEVERE [global]
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method)
	at java.lang.Thread.start(Thread.java:640)
	at java.awt.EventQueue.initDispatchThread(EventQueue.java:904)
[catch] at java.awt.EventDispatchThread.run(EventDispatchThread.java:153)
Comment 1 tnleeuw 2013-01-09 14:45:24 UTC 
NB: JVM version used is JDK 1.6.35 & 1.6.38 32-bits.
Comment 2 Martin Entlicher 2013-01-09 17:15:05 UTC 
Already fixed by http://hg.netbeans.org/main-golden/rev/9a7876c49e5c
It should have already propagate into the dev build.
Comment 3 tnleeuw 2013-01-10 09:11:29 UTC 
I could not find this issue in Bugzilla, with my limited Bugzilla skills, which is why I decided to raise it... I will keep trying some Nightlies until I get one that works again.
(Current nightly 201301100107 is still broken, unfortunately)
Comment 4 tnleeuw 2013-01-17 11:14:16 UTC 
NetBeans Nightly of 201301160001 still refuses to start up, still throwing this same error.

Does that mean that the patch that should have fixed this issue is still not landed in the nightly builds?

Or does that mean that there's still a different issue out there, not fixed?

I wonder if I should reopen the issue or still wait?

I also wonder why I am affected by this problem, but appearently not everybody else is.
Comment 5 Martin Entlicher 2013-01-17 14:12:47 UTC 
I'm sorry, I did not realized, that the module uihandler.interactive is on an update center. Therefore it's necessary to increase it's module version in order to update the fix.

This is done in trunk by changeset:   244615:e9e53f954f1c
http://hg.netbeans.org/core-main/rev/e9e53f954f1c
and on release73 branch by changeset:   251819:c953a1eb03ca
http://hg.netbeans.org/releases/rev/c953a1eb03ca
Comment 6 tnleeuw 2013-01-17 14:19:08 UTC 
OK, thanks very much!

Any idea when this will make it into a Nightly Build? Or should something else be done (by me) in order to update the plugin in my installation?

All nightly builds are installed in their own directory and I don't usually install extra plugins; not sure though if any are installed in my profile directory instead of the installation directory.
Comment 7 Martin Entlicher 2013-01-17 14:36:38 UTC 
I hope that this change will get into the next Nightly Build, which also updates the plugins on UC. I guess that NetBeans will then notify you that there are plugins to update. There should be no need to install a new build.
Then in messages.log file you can verify that uihandler.interactive module has version 1.5 instead of the current 1.4.