[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (~1.5Mb [^test-150.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, having about 300 thousand characters in a single
element ([^test-30.fo]). But the high memory consumption isn't observed
when processing 250 thousand characters ([^test-25.fo]).
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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, having about 300 thousand characters in a single
element ([^test-30.fo]). But the high memory consumption isn't observed
when processing 250 thousand characters ([^test-25.fo]).
> 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-150.fo,
> test-25.fo, test-30.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (~1.5Mb [^test-150.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, having about 300 thousand characters in a
> single element ([^test-30.fo]). But the high memory consumption isn't
> observed when processing 250 thousand characters ([^test-25.fo]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raman Katsora updated FOP-2860:
---
Attachment: (was: test.fo)
> 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-150.fo,
> test-25.fo, test-30.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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, having about 300 thousand characters in a
> single element ([^test-30.fo]). But the high memory consumption isn't
> observed when processing 250 thousand characters ([^test-25.fo]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raman Katsora updated FOP-2860:
---
Attachment: test-150.fo
> 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-150.fo,
> test-25.fo, test-30.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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, having about 300 thousand characters in a
> single element ([^test-30.fo]). But the high memory consumption isn't
> observed when processing 250 thousand characters ([^test-25.fo]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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, having about 300 thousand characters in a single
element ([^test-30.fo]). But the high memory consumption isn't observed
when processing 250 thousand characters ([^test-25.fo]).
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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.
> 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-25.fo,
> test-30.fo, test.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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, having about 300 thousand characters in a
> single element ([^test-30.fo]). But the high memory consumption isn't
> observed when processing 250 thousand characters ([^test-25.fo]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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-25.fo,
> test-30.fo, test.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raman Katsora updated FOP-2860:
---
Attachment: test-30.fo
test-25.fo
> 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-25.fo,
> test-30.fo, test.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819010#comment-16819010 ] Juan commented on FOP-2855: --- Found out that [^issue_fix.patch]causes this: !issue_after_fix1.png! So added another patch based on the first one. > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.xml, issue_after_fix1.png, > issue_fix.patch, issue_fix_2.patch, issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan updated FOP-2855: -- Attachment: (was: issue_fixed.png) > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.xml, issue_after_fix1.png, > issue_fix.patch, issue_fix_2.patch, issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan updated FOP-2855: -- Attachment: issue_fix_2.patch issue_fixed.png issue.xml issue_after_fix1.png > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.xml, issue_after_fix1.png, > issue_fix.patch, issue_fix_2.patch, issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan updated FOP-2855: -- Attachment: (was: issue.xml) > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.xml, issue_after_fix1.png, > issue_fix.patch, issue_fix_2.patch, issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan updated FOP-2855: -- Attachment: (was: issue.png) > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.xml, issue_after_fix1.png, > issue_fix.patch, issue_fix_2.patch, issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2855) [PATCH] When using letter-spacing and white-space=pre inline elements after multiple spaces are sligthly moved to the right
[ https://issues.apache.org/jira/browse/FOP-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan updated FOP-2855: -- Attachment: issue.png > [PATCH] When using letter-spacing and white-space=pre inline elements after > multiple spaces are sligthly moved to the right > --- > > Key: FOP-2855 > URL: https://issues.apache.org/jira/browse/FOP-2855 > Project: FOP > Issue Type: Bug > Components: layout/inline >Affects Versions: trunk >Reporter: Juan >Assignee: Matthias Reischenbacher >Priority: Trivial > Attachments: issue.png, issue.png, issue.xml, issue_fix.patch, > issue_fixed.png > > > Inline elements inside code elements, that use white-space=pre and > letter-spacing > 0 (e.g. 1pt) are slightly moved to the right. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very high memory
consumption.
For instance, transforming a document with {{}} 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).
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} 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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very high memory
> consumption.
> For instance, transforming a document with {{}} 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).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} 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).
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} 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).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb).
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
> The heapdump shows 27.5 millions
> {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
> The heapdump shows 27.5 millions
> {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
The heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
A heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
!image-2019-04-16-10-07-53-502.png|thumbnail!
> 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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
> The heapdump shows 27.5 millions
> {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
A heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
!image-2019-04-16-10-07-53-502.png|thumbnail!
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
A heapdump shows 27.5 millions
{{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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
> A heapdump shows 27.5 millions
> {{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
> !image-2019-04-16-10-07-53-502.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
For instance, transforming a document with {{}} containing 1.5
million characters (.fo is about 1.5Mb [^test.fo]) requires about 3Gb of RAM.
A heapdump shows 27.5 millions
{{org.apache.fop.layoutmgr.BreakingAlgorithm.KnuthNode}} (~2.6Gb)
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
> 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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> For instance, transforming a document with {{}} containing 1.5
> million characters (.fo is about 1.5Mb [^test.fo]) 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
> 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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> Transforming a document with {{}} 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
https://issues.apache.org/jira/browse/FOP-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raman Katsora updated FOP-2860:
---
Attachment: test.fo
> 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.fo
>
>
> when a single element (e.g. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> Transforming a document with {{}} 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
was:
when a single element (e.g. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
> 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. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> Transforming a document with {{}} 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. {{}}) contains a sufficiently large
amount of text, the fo-to-pdf transformation causes very large memory
consumption.
Transforming a document with {{}} 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)
was:
when a single element (e.g. ) contains a sufficiently large amount of
text, the fo-to-pdf transformation causes very large memory consumption.
Transforming a document with 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)
> 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. {{}}) contains a sufficiently large
> amount of text, the fo-to-pdf transformation causes very large memory
> consumption.
> Transforming a document with {{}} 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. ) contains a sufficiently large amount of
text, the fo-to-pdf transformation causes very large memory consumption.
Transforming a document with 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)
was:
when a single element (e.g. ) contains a sufficiently large amount of
text, the fo-to-pdf transformation causes very large memory consumption.
Transforming a document with 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)
!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. ) contains a sufficiently large amount
> of text, the fo-to-pdf transformation causes very large memory consumption.
> Transforming a document with 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)
[jira] [Updated] (FOP-2860) BreakingAlgorithm causes high memory consumption
[
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. ) contains a sufficiently large amount
> of text, the fo-to-pdf transformation causes very large memory consumption.
> Transforming a document with 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)
[jira] [Created] (FOP-2860) BreakingAlgorithm causes high memory consumption
Raman Katsora created FOP-2860:
--
Summary: 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
when a single element (e.g. ) contains a sufficiently large amount of
text, the fo-to-pdf transformation causes very large memory consumption.
Transforming a document with 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)
