-
Bug
-
Resolution: Fixed
-
P2
-
7
The attached test has a JFrame wtih setDefaultCloseOperation set to JFrame.EXIT_ON_CLOSE.
1)Compile the test and and execute the test on Vista 6000 Ultimate
2)Click on the Close button of the Frame in the Top Right corner.
Expected Behavior
The JFrame closes and the java process exits
Actual Behavior
The JFrame closes but the java process does not exit, the process ID can still be seen in The task manager.
I tried with a simple awt frame with a windowListener for closing the window and the same buggy behavior was seen.
The test and the thread dump for the same are attached to the bug report.
This behavior is specific to Vista and is not occuring on Windows Xp.
I could trace this back to jdk 7.0 build 02.
It is not reproducible with 7.0 build 01.
1)Compile the test and and execute the test on Vista 6000 Ultimate
2)Click on the Close button of the Frame in the Top Right corner.
Expected Behavior
The JFrame closes and the java process exits
Actual Behavior
The JFrame closes but the java process does not exit, the process ID can still be seen in The task manager.
I tried with a simple awt frame with a windowListener for closing the window and the same buggy behavior was seen.
The test and the thread dump for the same are attached to the bug report.
This behavior is specific to Vista and is not occuring on Windows Xp.
I could trace this back to jdk 7.0 build 02.
It is not reproducible with 7.0 build 01.
- duplicates
-
JDK-6526272 Java process is not terminating after a display mode change, on WinXP
- Closed
- relates to
-
JDK-6387273 JDialog makes browsers crash in mustang b59
- Closed
-
JDK-6660258 Java application stops Windows logout/shutdown (regression in 1.5.0_14)
- Closed