JDK-6927458 : font system should cache transient strikes with weak references.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-02-17
  • Updated: 2020-04-07
  • Resolved: 2011-03-08
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.
6u21Fixed 7 b126Fixed
Related Reports
Duplicate :  
Since many different rotation or general transforms may used for a glyph
during animation scenarios, we should be caching these more weakly to
faster reclaim native and Java heap. Presently we use Soft references
which are reclaimed only when the heap cannot be expanded.
There is of course a trade off against performance as subsequent uses
may exist and if they come after a GC, we need to re-create the glyph.
However in testing this seems acceptable given the potential benefit to
more stable memory use. And the reduced GC load actually helps performance in
high memory usage scenarios.

EVALUATION http://hg.openjdk.java.net/jdk7/build/jdk/rev/4e47e55dd717

EVALUATION This doesn't fix 6893655, although it should make it significantly less likely to be encountered in any real app and is a very simple change.