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.
ArrayIndexOutOfBoundsException is reported after successful plugins installation. I am using netbeans-trunk-nightly-200911251400-ml-javase-windows.exe and java card plugins distributed 11/17. To reproduce select "Tools/Plugins/Downloaded", choose all plugins and confirm installation. After successful installation this exception is reported: java.lang.ArrayIndexOutOfBoundsException: 0 at javax.swing.text.BoxView.getOffset(BoxView.java:1084) at javax.swing.text.BoxView.childAllocation(BoxView.java:678) at javax.swing.text.CompositeView.getChildAllocation(CompositeView.java:215) at javax.swing.text.BoxView.getChildAllocation(BoxView.java:436) at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.calculateViewPosition(BasicTextUI.java:1979) at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.layoutContainer(BasicTextUI.java:1955) at java.awt.Container.layout(Container.java:1421) at java.awt.Container.doLayout(Container.java:1410) at java.awt.Container.validateTree(Container.java:1507) at java.awt.Container.validateTree(Container.java:1513) at java.awt.Container.validateTree(Container.java:1513) at java.awt.Container.validate(Container.java:1480) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:670) [catch] at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:127) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:125) 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) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) It doesn't seem to cause any additional problems. It most likely not javacard specific and may already be reported in other category, but I didn't find it.
I reinstalled Netbeans few times to check different conditions, it turns out this exception is not reported every time, just in most cases.
There's basically no NetBeans code in this stack trace; any chance you were using JDK 7? I've seen similar exceptions there. It probably is a duplicate of something that was fixed some way or other, as I have not seen this exception in some time. FYI, if, when you get one of these exceptions, you use Review and Report Problem in the exception dialog, then the server will pattern-match the stack trace against all stack traces in known bug reports. It is very good at identifying duplicates, so this can save you some time. When it gives you back the stack trace URL, you can always file a bug with it for me immediately, rather than wait for the script to see it a threshold number of times and create a bug for you.
> There's basically no NetBeans code in this stack trace; any chance you were > using JDK 7? I've seen similar exceptions there. Its some service thread responsible for GUI. Still, it can be wrong update of GUI objects done somewhere else. Java: Java(TM) SE Runtime Environment (build 1.6.0_12-b04) Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode, sharing) > It probably is a duplicate of something that was fixed some way or other, as I > have not seen this exception in some time. I seen it 2 times today (out of 5) with latest netbeans/plugins. This exception is not reliable, it can be related to timing/thread scheduling. "Review and Report Problem" is probably a right choice in this case.