Details
-
Bug
-
Resolution: Won't Fix
-
P3
-
6
-
x86
-
windows_xp
Description
FULL PRODUCT VERSION :
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
and
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
A java swing application running under Windows XP can cause the operating system to freeze completely for a long time (20-40 sec).
During that time not only the java application is blocked but the entire system is frozen.
Additionally, some but not all users report that after the freeze the Swing application does not repaint properly (often displaying black areas, but sometimes even colourful static).
Using -Dsun.java2d.noddraw=true does prevent an application from causing hangs.
In order to reproduce this bug it seems necessary that at least one java process runs for a long time (~24h). However, after the first freeze occured the chance increases to see it more often (until the next reboot).
For details please see http://forums.java.net/jive/thread.jspa?threadID=15115 ("Mustang: Swing apps freeze then painting corrupt")
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please see discussion at http://forums.java.net/jive/thread.jspa?threadID=15115 ("Mustang: Swing apps freeze then painting corrupt")
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
No Java application should cause the operating system to freeze.
ACTUAL -
Java applications are able to cause a freeze of the operating system.
REPRODUCIBILITY :
This bug can be reproduced often.
CUSTOMER SUBMITTED WORKAROUND :
None - only a reboot of the whole machine helps!
Release Regression From : 5.0u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
Release Regression From : mustang
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
and
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
A java swing application running under Windows XP can cause the operating system to freeze completely for a long time (20-40 sec).
During that time not only the java application is blocked but the entire system is frozen.
Additionally, some but not all users report that after the freeze the Swing application does not repaint properly (often displaying black areas, but sometimes even colourful static).
Using -Dsun.java2d.noddraw=true does prevent an application from causing hangs.
In order to reproduce this bug it seems necessary that at least one java process runs for a long time (~24h). However, after the first freeze occured the chance increases to see it more often (until the next reboot).
For details please see http://forums.java.net/jive/thread.jspa?threadID=15115 ("Mustang: Swing apps freeze then painting corrupt")
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please see discussion at http://forums.java.net/jive/thread.jspa?threadID=15115 ("Mustang: Swing apps freeze then painting corrupt")
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
No Java application should cause the operating system to freeze.
ACTUAL -
Java applications are able to cause a freeze of the operating system.
REPRODUCIBILITY :
This bug can be reproduced often.
CUSTOMER SUBMITTED WORKAROUND :
None - only a reboot of the whole machine helps!
Release Regression From : 5.0u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
Release Regression From : mustang
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.