-
Bug
-
Resolution: Unresolved
-
P4
-
5.0, 7
-
Cause Known
-
generic
-
generic
Name: agR10216 Date: 02/04/2004
The bug 4984970 revealed a synchronization issue with
Component.{max|min|pref}Size and Component.{max|min|pref}SizeSet.
For example, if setMaximumSize() and invalidate() are called on
two different threads at the same time, it's possible for the
component to get into an inconsistent state (the field maxSize
is null, but the field maxSizeSet is true), and a subsequent
call to getMaximumSize() will result in NullPointerException.
###@###.### 2004-02-04
======================================================================
- relates to
-
JDK-4984970 Java2Demo threw exception in win2003-amd
- Closed
-
JDK-6884934 b4723783 fails due to StringIndexOutOfBoundsException
- Closed
-
JDK-4864304 Improve memory consumption of Swing apps
- Resolved