JDK-2156508 : SurfaceData should not initialize Ductus until needed
  • Type: Backport
  • Backport of: JDK-6633796
  • Component: client-libs
  • Sub-Component: 2d
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • Submitted: 2007-11-29
  • Updated: 2011-02-11
  • Resolved: 2011-02-09
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
6u10Fixed 7Resolved
Comments
EVALUATION The fix that was integrated into JDK6 for this problem doesn't directly apply to the state of the code in JDK7 since we integrated a "pluggable rendering engine" mechanism into JDK7. Forward porting this would involve inventing a different fix to lazily load the library. Fortunately, experiments on JDK7 show that we no longer load the Ductus library unless it is actually needed to do some work. This only tends to happen if you use antialiasing, wide lines (or any wide stroked path), and sometimes if you use alpha rendering. In those cases we actually need services from the Ductus native library so it isn't a mistake to load the library under those conditions. These are the same conditions that JDK6 would have loaded the native library even after the original fix for this problem and for the same reasons so that behavior is not a regression. As a result, no forward port of this fix to JDK7 is needed. I am closing the JDK7 MR version of this bug as "not reproducible".
09-02-2011