Details
-
Bug
-
Resolution: Fixed
-
P3
-
7, 8u144, 11, 12
-
b20
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8221627 | 11.0.4-oracle | Sergey Bylokhov | P3 | Resolved | Fixed | b02 |
JDK-8220054 | 11.0.4 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8221679 | 11.0.2 | Sergey Bylokhov | P3 | Closed | Fixed | b32 |
JDK-8219672 | openjdk8u212 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8224361 | emb-8u221 | Sergey Bylokhov | P3 | Resolved | Fixed | master |
JDK-8224153 | openjdk7u | Sergey Bylokhov | P3 | Resolved | Fixed | master |
Description
1. If the java window gets "WINDOW_ACTIVATED" event it will try to send "WINDOW_DEACTIVATED" to the old active window, which is stored in the "activeWindow" field.
2. If the java component lost the focus, and the opposite component is not a java component, then it will try to send "WINDOW_DEACTIVATED" to the old active window, which is stored in the "activeWindow" field.
The difference in these two cases is that in "case 1" we check the old active window to null[1], and the second case has no such check. The bug is reproduced in non-standalone mode, when we have a few Appcontexts and this field might be updated by different EDT in parallel.
Note that the test is for OSX only, because of another bug:
[1] http://hg.openjdk.java.net/jdk/jdk/file/ad9077f044be/src/java.desktop/share/classes/java/awt/DefaultKeyboardFocusManager.java#l527
[2] https://bugs.openjdk.java.net/browse/JDK-8204142
Attachments
Issue Links
- backported by
-
JDK-8219672 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Resolved
-
JDK-8220054 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Resolved
-
JDK-8221627 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Resolved
-
JDK-8224153 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Resolved
-
JDK-8224361 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Resolved
-
JDK-8221679 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source
- Closed
- relates to
-
JDK-8204142 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.
- Resolved
- links to