-
Bug
-
Resolution: Cannot Reproduce
-
P5
-
None
-
1.4.0
-
None
-
x86
-
windows_nt
This is essentially a reopening of bug 4690117.
If you uncomment out the code in FullScreenTest*.java (including the
println statements) run the app, and alt-tab out of it, you will notice that
the app is stuck in an infinite loop trying to validate the volatile image.
The VolatileImage code should return an image that is validated (ie,
contentsLost() will return false). But it appears that if we alt-tab out
of the application and there is a problem creating teh vram-version of the
image, then the flags never get reset and the application is stuck in a loop
waiting for the image to be correctly restored.
If you uncomment out the code in FullScreenTest*.java (including the
println statements) run the app, and alt-tab out of it, you will notice that
the app is stuck in an infinite loop trying to validate the volatile image.
The VolatileImage code should return an image that is validated (ie,
contentsLost() will return false). But it appears that if we alt-tab out
of the application and there is a problem creating teh vram-version of the
image, then the flags never get reset and the application is stuck in a loop
waiting for the image to be correctly restored.
- relates to
-
JDK-4690117 VolatileImage never recovers lost surface in FullScreenTest
-
- Closed
-