Running Java2Demo and resizing the application window to very large or maximum size will (on occasion) generate java.lang.ArrayIndexOutOfBoundsException.

- The bug is easier to reproduce when the demo is running the Transforms demo set when the resize occurs.

- This is more of a stress test and may not happen for normal use. The bug has been seen on multiple platforms with recent tiger build: 1.5.0-rc-b63 (Solaris and Linux platforms):

Solaris10 (d2-sunblade)
Cinnabar-SPARC (d2-u60-1)
Cinnabar-x86 (awt-sqe6)

- The bug is very similar (and may be related) to bug 4902189 (but for this bug it always occurs at:
"at java2d.MemoryMonitor$Surface.paint(MemoryMonitor.java:241)" during a window resize. The earlier parts of the stack trace are similar.

-------------------- Running Java2Demo
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: 100
at java2d.MemoryMonitor$Surface.paint(MemoryMonitor.java:241)
at javax.swing.JComponent.paintWithOffscreenBuffer(JComponent.java:4930)
at javax.swing.JComponent.paintDoubleBuffered(JComponent.java:4883)
at javax.swing.JComponent._paintImmediately(JComponent.java:4826)
at javax.swing.JComponent.paintImmediately(JComponent.java:4633)
at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:451)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:114)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)


Steps to reproduce (The bug will occur randomly when resized)
==================
1) Launch Java2Demo with recent Tiger build
2) Use the demo and cycle through some of the demo panels (use the controls)
3) Minimize the application window to a very small size.
4) Maximuze the window manually to very large size (or click the window maximum box).
5) The exception may occur 1 out of 7 or 8 times and is unrecoverable as the user will need to cntl-c to exit