You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Michael Prieß (JIRA)" <ji...@apache.org> on 2016/11/09 13:13:58 UTC
[jira] [Commented] (FOP-2525) [PATCH] Excessive memory usage when
using truetype collection (.ttc)
[ https://issues.apache.org/jira/browse/FOP-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650890#comment-15650890 ]
Michael Prieß commented on FOP-2525:
------------------------------------
Is there any planned date?
> [PATCH] Excessive memory usage 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
> Assignee: simon steiner
> Priority: Minor
> Attachments: FOP-2525.patch, FOP_patch_heap-usage.png, removestatic2.patch
>
>
> 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)