JDK-6666931 : D3D/OGL: BufferedContext.invalidateContext doesn't reset native state
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-22
  • Updated: 2010-10-14
  • 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.
6u10 b13Fixed
Related Reports
Relates :  
The BufferedContext.invalidateContext() only resets the state of the 
BufferedContext, but not the native one. This may lead to 
de-synchronization between these.

For example, if a transform is set, and then context is invalidated,
the native device may have the transform set.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/java2d_data/6u10/6666931.0

EVALUATION We need to reset the native state (transform, clip, etc). This bug was uncovered by the fix for 6664068 where we sometimes invalidate the context.