United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6878284 Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
6878284 : Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"

Details
Type:
Bug
Submit Date:
2009-09-02
Status:
Closed
Updated Date:
2012-10-01
Project Name:
JDK
Resolved Date:
2010-01-13
Component:
client-libs
OS:
generic
Sub-Component:
java.awt
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
6u18
Fixed Versions:
6u18

Related Reports
Backport:
JDK-2182717 - Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
Relates:
JDK-6839727 - java plugin should avoid relaunch of jvm if possible
Relates:
JDK-6809246 - EventDispatchThread shouldn't be reinitialized for disposed AppContexts

Sub Tasks

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/
2009-09-04 
EVALUATION

The fix is to have addtional check for AppContext.isDisposed to avoid recreating EDT during shutdown.
2009-09-04


Hardware and Software, Engineered to Work Together