[ https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raman Katsora updated FOP-2860: ------------------------------- Description: when a single element (e.g. {{<fo:block>}}) contains a sufficiently large amount of text, the fo-to-pdf transformation causes very high memory consumption. For instance, transforming a document with {{<fo:block>}} containing 1.5 million characters (~1.5Mb [^test.fo]) requires about 3Gb of RAM. The heapdump shows 27.5 million {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb). We start observing this issue when having about 300 thousand characters within a single element. was: when a single element (e.g. {{<fo:block>}}) contains a sufficiently large amount of text, the fo-to-pdf transformation causes very high memory consumption. For instance, transforming a document with {{<fo:block>}} containing 1.5 million characters (~1.5Mb [^test.fo]) requires about 3Gb of RAM. The heapdump shows 27.5 million {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb). > BreakingAlgorithm causes high memory consumption > ------------------------------------------------ > > Key: FOP-2860 > URL: https://issues.apache.org/jira/browse/FOP-2860 > Project: FOP > Issue Type: Bug > Affects Versions: 2.3 > Reporter: Raman Katsora > Priority: Critical > Attachments: image-2019-04-16-10-07-53-502.png, test-250000.fo, > test-300000.fo, test.fo > > > when a single element (e.g. {{<fo:block>}}) contains a sufficiently large > amount of text, the fo-to-pdf transformation causes very high memory > consumption. > For instance, transforming a document with {{<fo:block>}} containing 1.5 > million characters (~1.5Mb [^test.fo]) requires about 3Gb of RAM. > The heapdump shows 27.5 million > {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb). > We start observing this issue when having about 300 thousand characters > within a single element. -- This message was sent by Atlassian JIRA (v7.6.3#76005)