-
Bug
-
Resolution: Fixed
-
P4
-
5.0
-
b36
-
x86
-
windows_nt
This was originally filed as part of bug 4945756, but the causes of this failure
are completely different than the causes for the failure of CycleDMImage.
D3dTranslucencyRestoration fails because we attempt to go into a display mode
of 640 x 480 x 32 x REFRESH_RATE_UNKNOWN. This can fail on any Windows
system which either:
- does not support 32 bpp depth
- does not support ddraw. Although REFRESH_RATE_UNKNOWN is sufficient
for a ddraw-performed display mode switch, it does not work for the
GDI equivalent. Instead you must supply a refresh rate that is valid
on this device.
In either of the above cases, the test will fail with an IllegalArgumentException: Invalid display mode.
See the stack trace in:
/net/jtgb4u4c.sfbay/export/sail15/results.2/tiger/b25/regtest/win32/win2003_linux-19/workDir/test/sun/java2d/DirectX/D3dTranslucencyRestoration.jtr
How to reproduce:
cd to a Tiger workspace
cd test/sun/java2d/DirectX
java -Dsun.java2d.noddraw=true D3dTranslucencyRestoration
are completely different than the causes for the failure of CycleDMImage.
D3dTranslucencyRestoration fails because we attempt to go into a display mode
of 640 x 480 x 32 x REFRESH_RATE_UNKNOWN. This can fail on any Windows
system which either:
- does not support 32 bpp depth
- does not support ddraw. Although REFRESH_RATE_UNKNOWN is sufficient
for a ddraw-performed display mode switch, it does not work for the
GDI equivalent. Instead you must supply a refresh rate that is valid
on this device.
In either of the above cases, the test will fail with an IllegalArgumentException: Invalid display mode.
See the stack trace in:
/net/jtgb4u4c.sfbay/export/sail15/results.2/tiger/b25/regtest/win32/win2003_linux-19/workDir/test/sun/java2d/DirectX/D3dTranslucencyRestoration.jtr
How to reproduce:
cd to a Tiger workspace
cd test/sun/java2d/DirectX
java -Dsun.java2d.noddraw=true D3dTranslucencyRestoration