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 6.1 (Build 200805300101) VM: Java HotSpot(TM) Client VM, 1.6.0_01-b06, Java(TM) SE Runtime Environment, 1.6.0_01-b06 OS: Windows XP, 5.1, x86 User Comments: dante: Drag & drop ejb method onto blank page GUEST: Creating JunitTest GUEST: Laoding netbeans 6.0 for the ve3ry first time so I could work with the GUI tutorial. avega: Open my Form , was create with netbeans 5.5.1 GUEST: opened a grails project in NetBeans with the latest "groovy and grails" plugin Stacktrace: java.lang.InternalError: Espa�o insuficiente de armazenamento para processar este comando. at sun.awt.windows.WToolkit.eventLoop(WToolkit.java:0) at sun.awt.windows.WToolkit.run(WToolkit.java:290) at java.lang.Thread.run(Thread.java:619)
Created attachment 71007 [details] stacktrace
Build: NetBeans IDE 6.1 (Build 200805300101) VM: Java HotSpot(TM) Client VM, 1.6.0_01-b06, Java(TM) SE Runtime Environment, 1.6.0_01-b06 OS: Windows XP, 5.1, x86 User Comments: Stacktrace: java.lang.InternalError: Espa�o insuficiente de armazenamento para processar este comando. at sun.awt.windows.WToolkit.eventLoop(WToolkit.java:0) at sun.awt.windows.WToolkit.run(WToolkit.java:290) at java.lang.Thread.run(Thread.java:619)
Created attachment 71008 [details] stacktrace
Reassigning to core/AWT for evaluation. Isn't it some known JDK bug?
I couldn't find any such error in JDK database. Apparently it looks like a problem in JDK windows toolkit, but exceptions reporter seems to not provide enough information to try anything. Error on line 0 - sun.awt.windows.WToolkit.eventLoop(WToolkit.java:0) is strange, there is usually no code at line 0 that could cause exception or an error. We would need to know from reporters: - Were there any exceptions earlier? - log file content (in <netbeans_dir>/etc/log) - Is the bug reproducible? Steps to reproduce then please - did netbeans hunp up or worked normally after this error? Please reopen with requested info, thank you.