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 200804211638) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13 OS: Windows Vista, 6.0, x86 User Comments: Statring IDE
Created attachment 63635 [details] stacktrace
Please attach steps to reproduce this issue, I can't reproduce. I guess this issue is random, unfortunately there is not enough info to find the source of the problem and fix. Please reopen if you have reproducible scenario, thank you.
Reopening - reproduced in NetBeans IDE Dev (Build 200810041417) http://statistics.netbeans.org/exceptions/detail.do?id=124841
After updating auto update center plugins, I got about 70 more updates - one of them seems to make an invalid assignment to an exeption's cause :( Probably it is the Groovy & Grails plugin (I've already had problems with it, but that does not necessarily imply that this bug is related to the module, of course). The problem here is the missing stack trace because of the Runnable ...
While working with NB, I've noticed that the exception occurs while selecting text or moving the mouse (don't know, if it matters: I'm currently editing xslt files).
Sorry for being so blind: The bug is in openide.loaders (it has its own awt package). It happens because of a ClassNotFoundException. This exception sets its Throwable cause to null; it cannot be initialized then, as an uninitialized cause is signalled by t.getCause() = t If this is fixed, the "correct" error message will help further.
This bug is popping up again and again, cannot say why (because of #150969), thus IDE looks instable. Having it in daily buid 200810211401, so I cannot tell if it's in RC1, too. Otherwise, I would have set this bug to P1 (IDE shouldn't be released with this bug!). Will test this with RC build only after #150969 has been fixed.
wasn't it fixed as part of 150969?
Please epdv, could you verify, that the issue is fixed?
150969 is now fixed and no newer reports here, so I assume problem was solved somehow. Please reopen with additional info if bug strikes again - now when 150969 is fixed we should know better where the bug is.