JDK-6878284 : Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u18
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: x86
  • Submitted: 2009-09-02
  • Updated: 2013-11-01
  • Resolved: 2010-01-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u18 b03Fixed 7Fixed
Related Reports
Relates :  
JDK-6839727 - java plugin should avoid relaunch of jvm if possible
Relates :  
JDK-6809246 - EventDispatchThread shouldn't be reinitialized for disposed AppContexts
Description
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())
Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/awt_data/6u18/6878284/
04-09-2009
EVALUATION The fix is to have addtional check for AppContext.isDisposed to avoid recreating EDT during shutdown.
04-09-2009