JDK-6663447 : D3D: excessive surface data replacements
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-02-14
  • Updated: 2011-01-20
  • Resolved: 2008-03-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10 b13Fixed 7Fixed
Related Reports
Relates :  
JDK-6655001 - D3D/OGL: Window translucency doesn't work with accelerated pipelines
Description
After the fix for 6655001 the replaceSurfaceData is called excessively, leading
to regression test failures because of OOMEs.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/build/jdk/rev/12b65e7ee3e4
04-12-2010
SUGGESTED FIX http://sa.sfbay.sun.com/projects/java2d_data/6u10/6663447.0
15-02-2008
EVALUATION We need to only replace the surface data when the current transparency/translucency status of the window changes from opaque to non-opaque/translucent. Currently we replace it even if the transparency factor is changed.
14-02-2008