-
Bug
-
Resolution: Fixed
-
P2
-
6u18
-
b03
-
x86
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2182717 | 7 | Dmitry Cherepanov | P3 | Resolved | Fixed | b74 |
Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
Usually, it takes up to 10 attempts to reproduce this "hang".
The hang/waiting happens during call targetAppContext.dispose().
The sequence of the appContext disposal is following
(a) ThreadGroup.interrupt
(b) ThreadGroup.stop
(c) ThreadGroup.destroy
Debugging log reveals that this "hang" happens during ThreadGroup.destroy call
and occurs only when AWT creates additional EDT threads during the disposal.
This should be fixed by additional check for AppContext.isDisposed() just before EDT creation (EventQueue.initDispatchThread())
Usually, it takes up to 10 attempts to reproduce this "hang".
The hang/waiting happens during call targetAppContext.dispose().
The sequence of the appContext disposal is following
(a) ThreadGroup.interrupt
(b) ThreadGroup.stop
(c) ThreadGroup.destroy
Debugging log reveals that this "hang" happens during ThreadGroup.destroy call
and occurs only when AWT creates additional EDT threads during the disposal.
This should be fixed by additional check for AppContext.isDisposed() just before EDT creation (EventQueue.initDispatchThread())
- backported by
-
JDK-2182717 Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
- Resolved
- relates to
-
JDK-6809246 EventDispatchThread shouldn't be reinitialized for disposed AppContexts
- Closed
-
JDK-6839727 java plugin should avoid relaunch of jvm if possible
- Closed