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 7568 - ArrayIndexOutOfBoundsException thrown after IDE restart
Summary: ArrayIndexOutOfBoundsException thrown after IDE restart
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P4 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-09-04 11:31 UTC by Martin Balin
Modified: 2008-12-23 10:54 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Balin 2000-09-04 11:31:30 UTC
JDK 1.3, FCS build.
Build 1091.

Steps:
1. Run IDE and open MemoryView and Ted forms. Both forms are automatically
marked as modified.
2. ComponentInspector contains two tabs with properties for both forms.
3. Clse IDE and confirm save for changed forms.
4. Start IDE.
5. After IDE is started following exception is thrown and ComponentInspector
window is not displayed:

Mon Sep 04 12:22:42 CEST 2000java.lang.ArrayIndexOutOfBoundsException: 1 > 0
java.lang.ArrayIndexOutOfBoundsException: 1 > 0
        at java.util.Vector.insertElementAt(Vector.java:551)
        at javax.swing.JTabbedPane.insertTab(JTabbedPane.java:441)
        at javax.swing.JTabbedPane.addTab(JTabbedPane.java:480)
        at
org.netbeans.core.windows.MultiTabContainer.setVisible(MultiTabContainer.java:429)
        at org.netbeans.core.windows.ModeImpl.setVisible(ModeImpl.java:468)
        at
org.netbeans.core.windows.ModeImpl$1.performCommand(ModeImpl.java:218)
        at
org.netbeans.core.windows.DeferredPerformer.processCommand(DeferredPerformer.java:161)
        at
org.netbeans.core.windows.DeferredPerformer.putRequest(DeferredPerformer.java:73)
        at org.netbeans.core.windows.ModeImpl.dockInto(ModeImpl.java:190)
        at
org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.doOpen(WindowManagerImpl.java:899)
        at
org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.open(WindowManagerImpl.java:856)
        at org.openide.windows.TopComponent.open(TopComponent.java:185)
        at org.openide.explorer.ExplorerPanel.open(ExplorerPanel.java:80)
        at
org.netbeans.modules.form.FormEditor$ComponentInspector.open(FormEditor.java:476)
        at org.netbeans.core.windows.ModeImpl.performCommand(ModeImpl.java:836)
        at
org.netbeans.core.windows.DeferredPerformer.processCommand(DeferredPerformer.java:161)
        at
org.netbeans.core.windows.DeferredPerformer.stateChanged(DeferredPerformer.java:111)
        at
org.netbeans.core.windows.StateManager.fireStateChanged(StateManager.java:112)
        at
org.netbeans.core.windows.StateManager.setVisibilityState(StateManager.java:137)
        at
org.netbeans.core.windows.StateManager.componentShown(StateManager.java:147)
        at java.awt.Component.processComponentEvent(Component.java:3604)
        at java.awt.Component.processEvent(Component.java:3556)
        at java.awt.Container.processEvent(Container.java:1165)
        at java.awt.Window.processEvent(Window.java:777)
        at java.awt.Component.dispatchEventImpl(Component.java:2593)
        at java.awt.Container.dispatchEventImpl(Container.java:1214)
        at java.awt.Window.dispatchEventImpl(Window.java:912)
        at java.awt.Component.dispatchEvent(Component.java:2497)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:333)
        at
java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:103)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:84)
Comment 1 Tomas Pavek 2000-09-04 14:18:59 UTC
I haven't succeded in reproducing this. BTW I wonder what means the sentence:
> ComponentInspector contains two tabs with properties for both forms.
(Component inspector should be always a single window.)

So could this be some problem in core (window system)?
Comment 2 David Simonek 2001-01-18 11:23:59 UTC
The code that caused this exception was rewritten from the scratch, so this
error is probably gone. Please reopen if you encounter this bug again.
Comment 3 Quality Engineering 2003-07-01 16:02:05 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 4 Quality Engineering 2003-07-01 16:26:04 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.