[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption

simon steiner (Jira)

     [ https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raman Katsora updated FOP-2860:
-------------------------------
    Attachment: image-2019-04-16-10-07-53-502.png

> 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
>
>
> when a single element (e.g. <fo:block>) contains a sufficiently large amount of text, the fo-to-pdf transformation causes very large memory consumption.
> Transforming a document with <fo:block> containing 1.5 million characters (.fo is about 1.5Mb) requires about 3Gb of RAM.
> A heapdump shows 27.5 millions {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)