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.
I install Netbeans build 138, close the explorer and reopen it. From that point onward I get this exception no matter what I do: Tue Mar 06 22:06:34 EST 2001java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 at java.lang.RuntimeException.<init>(RuntimeException.java:49) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.get(ArrayList.java(Compiled Code)) at org.netbeans.core.windows.frames.PerimeterLayout.setPeriCompBounds(Perime terLayout.java:248) at org.netbeans.core.windows.frames.PerimeterLayout.layoutContainer(Perimete rLayout.java:225) at java.awt.Container.layout(Container.java(Compiled Code)) at java.awt.Container.doLayout(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validate(Container.java:734) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java: 319) [catch] at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEven tQueueUtilities.java:204) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:160) at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code)) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java(Compil ed Code)) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java(Compiled Code)) at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
winsys
Duplicate, workaround is to close the IDE and restart. And sure, I will try to fix it quickly. *** This issue has been marked as a duplicate of 9885 ***
I get the following exception with build 147. You marked this bug a duplicate of bug #9885 which was closed yet this bug remains unresolved.. Fri Mar 16 19:11:35 EST 2001java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 at java.lang.RuntimeException.<init>(RuntimeException.java:49) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.get(ArrayList.java(Compiled Code)) at org.netbeans.core.windows.frames.PerimeterLayout.setPeriCompBounds(Perime terLayout.java:286) at org.netbeans.core.windows.frames.PerimeterLayout.layoutContainer(Perimete rLayout.java:263) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validate(Container.java(Compiled Code)) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java: 319) at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEven tQueueUtilities.java:204) [catch] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java(Compiled Code)) at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code)) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java(Compil ed Code)) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java(Compiled Code)) at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
I get an IndexOutOfBoundsException if I: 1) Compile 2) Close output window 3) Compile again (causing the output window to reappear an exception to be thrown). Is this bug being looked at? It's set to P1 priority yet no one has touched it ever since it was marked as DUPLICATE even though I changed it back.. Give me a sign you're still alive ;)
Dev build of NB #168 - it seems that it works, no exception is thrown ;-) Can you check it please on OS2. Thx.
Still occurs here on build168. I get two exceptions this time: --------------- Tue Apr 17 17:53:52 EDT 2001: java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 at java.lang.RuntimeException.<init>(RuntimeException.java:49) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.get(ArrayList.java(Compiled Code)) at org.netbeans.core.windows.frames.PerimeterLayout.setPeriCompBounds(Perime terLayout.java:286) at org.netbeans.core.windows.frames.PerimeterLayout.layoutContainer(Perimete rLayout.java:263) at java.awt.Container.layout(Container.java(Compiled Code)) at java.awt.Container.doLayout(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validate(Container.java(Compiled Code)) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java: 319) at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEven tQueueUtilities.java:204) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java(Compiled Code)) at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code)) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java(Compil ed Code)) [catch] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:99) at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) -------------------- #2: Tue Apr 17 17:54:51 EDT 2001: java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 java.lang.IndexOutOfBoundsException: Index: -1, Size: 5 at java.lang.RuntimeException.<init>(RuntimeException.java:49) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.RangeCheck(ArrayList.java(Compiled Code)) at java.util.ArrayList.get(ArrayList.java(Compiled Code)) at org.netbeans.core.windows.frames.PerimeterLayout.setPeriCompBounds(Perime terLayout.java:286) at org.netbeans.core.windows.frames.PerimeterLayout.layoutContainer(Perimete rLayout.java:263) at java.awt.Container.layout(Container.java(Compiled Code)) at java.awt.Container.doLayout(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validateTree(Container.java(Compiled Code)) at java.awt.Container.validate(Container.java(Compiled Code)) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java: 319) at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEven tQueueUtilities.java:204) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java(Compiled Code)) at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code)) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java(Compil ed Code)) [catch] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:99) at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) ----------------- Hope this helps..
It looks like this occurs only on OS2, moreover it may be problem of IBM JVM. On Solaris I was unable to reproduce it. Assigning to Dafe. Someone reported similary problem against ibm jdk on windows.
Lowering to P2, because IBM's JVM is not oficially supported. Fixing will take longer time, I will need to get ibm's jvm running.
geez ;) Ok, ok.. Is there anything I could run on my end to help this along?
Step forward: I'm running netbeans also on ibm's jvm 1.3.0 and I'm able to reproduce your problem without problems, so let's hope I can fix fix as well :-) So, confirming that this is problem specific to ibm's jvm.
fixed, indeed it was my fault - it worked on sun's JVM only due to some side effects.
Target milestone -> 3.3 Removing OPEN_IN_3.2 keyword.
*** Issue 15346 has been marked as a duplicate of this issue. ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.