[
https://issues.apache.org/jira/browse/FOP-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Rondelli updated FOP-2525:
---------------------------------
Comment: was deleted
(was: As for the subclasses they are:
GlyphPositioningTable (org.apache.fop.complexscripts.fonts)
GlyphSubstitutionTable (org.apache.fop.complexscripts.fonts)
GlyphDefinitionTable (org.apache.fop.complexscripts.fonts)
The hashCode and equals method needs to be implemented there as well. I can do
it.
The last part regarding the PDF output I don't understand. BTW I'm currently
suing this patch in production and works fine :))
> [PATCH] Memory leak present when using Truetype Collection (.ttc)
> -----------------------------------------------------------------
>
> Key: FOP-2525
> URL: https://issues.apache.org/jira/browse/FOP-2525
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: At least Mac and Linux, both Oracle VM and OpenJDK
> Reporter: Jeremy Smith
> Priority: Minor
> Attachments: FOP-2525.patch, FOP_patch_heap-usage.png
>
>
> When a TrueType Collection file is used to specify custom fonts, and a
> long-running FopFactory is used to create FOP instances to process many FO
> input documents, millions of
> org.apache.fop.complexscripts.fonts.GlyphPositioningTable$PairValues and
> org.apache.fop.complexscripts.fonts.GlyphPositioningTable$Values instances
> get created which are never collected. Thus the heap continues to grow,
> leading to eventual GC thrashing or crash.
> When the same fonts are used, but extracted from the TTC file, the issue does
> not occur, and the instances of those classes are collected normally.
> The issue can be seen by repeatedly processing a document with a config.xml
> which specifies fonts inside of a Truetype Collection file. Attaching
> VisualVM to such a process will show continuous heap growth and millions of
> aforementioned instances whose numbers never decrease.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
