#124 ArrayIndexOutOfBounds in RecipientList

[Wesley Tanaka]

stack traces to follow

[Wesley Tanaka]

Logged In: YES
user_id=11717

Exception occurred during event dispatching:
java.lang.ArrayIndexOutOfBoundsException: 17 >= 17
at java.util.Vector.elementAt(Vector.java:417)
at
javax.swing.DefaultListModel.getElementAt(DefaultListModel.java:70)
at
javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:709)
at
javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:660)
at
javax.swing.plaf.basic.BasicListUI.getPreferredSize(BasicListUI.java:169)
at javax.swing.JComponent.getPreferredSize(JComponent.java:990)
at
javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:752)
at java.awt.Container.layout(Container.java:686)
at java.awt.Container.doLayout(Container.java:676)
at java.awt.Container.validateTree(Container.java:750)
at java.awt.Container.validate(Container.java:728)
at
javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:313)
at
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:123)
at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)

[Wesley Tanaka]

Logged In: YES
user_id=11717

That stack trace came from jdk 1.1.7v3 (blackdown for
linux), and swing 1.1.1fcs.

I think it might not be battle.net specific. Instead, I
think it's because battle.net generates a lot of join/leave
events.

I will try making a fake client to reproduce this bug and
attach it here.

[Wesley Tanaka]

Logged In: YES
user_id=11717

This also happens with Linux JDK 1.3.1

[Wesley Tanaka]

Bug477956Client quickly creates and removes recipients and can be used to reproduce this bug.

[Wesley Tanaka]

Logged In: YES
user_id=11717

I've reproduced this without the battle.net client being
involved. The repro case involves instantiating and
"connect"ing the Bug477956Client protocol, and then
selecting and de-selecting it in the "clients" list in the
inline gui.

[Wesley Tanaka]

Logged In: YES
user_id=11717

Also reproduced on Windows Sun JRE 1.3.0_03

[Wesley Tanaka]

Logged In: YES
user_id=11717

This seems to be a swing problem, and it doesn't seem to be
hurting functionality. Lowering priority.

[Wesley Tanaka]

Patch to use Bug477956Client

[Wesley Tanaka]

Updated Bug477956Client