JDK-8036022 : D3D: rendering with XOR composite causes InternalError.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 7u51
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-02-28
  • Updated: 2014-10-15
  • Resolved: 2014-03-21
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 7 JDK 8 JDK 9
7u72Fixed 8u20Fixed 9 b08Fixed
Related Reports
Relates :  
Description
In case of d3d rendering with XOR composite causes an InternalError,
that indicates a problem in d3d->gdi fall back strategy.
 

Comments
assigned as bugdb assignment
2014-03-14

In case of XOR composite, rendering pipeline falls back from d3d to gdi. However, gdi surface data does not re-set rendering loops during validation, that leads to usage of the software loops (due to dst type mismatch), and results in observed internal error. Suggested fix forces the re-set of the rendering loops, at least for the case of XOR composite. Fix review: http://mail.openjdk.java.net/pipermail/2d-dev/2014-March/000001.html
2014-03-13

assigned as well done in bugDB
2014-02-28