JDK-8127853 : refactor MegaTexture and MegaCoords to have an ability to be explicitly disposed
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx2.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-02-01
  • Updated: 2015-06-17
  • Resolved: 2012-02-12
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.
Other
fx2.1Fixed
Related Reports
Blocks :  
JDK-8128766 - WebView fails to display very large images in d3d mode
Comments
fixed in changeset 15503 (82b490c8c6d5) fix RT-19363: implement direct (create\dispose) compound texture
12-02-2012
Vasiliy Baranov added a comment - Feb, 1 2012 05:26 PM It appears the added classes manage textures via ResourceFactory.getCachedTexture and do not allow for explicit texture disposal. It has been agreed that explicit disposal is the way to go for WebView for now, so I am re-opening this bug, humbly asking for an ability to explicitly dispose textures when using Mega{Coords|Image}.
01-02-2012