Hi,
In my experience FOP does a poor thing with long page sequences.
It seems to keep them in memory (for repagination maybe?) completely
Memory footprint for FOP goes down dramatically
if you have a logic that cuts the pages
Rather than using mechanisms such as break before
or similar, create new page sequences when you can
(eg. per chapter, ...)
That has helped me in the past
Cheers
Geert
At 16:33 15/08/2014, you wrote:
Hi All,
I know, difficult to say without having the
source, but could someone explain me why FOP
crashes, hangs (memory ?) for relative big
documents and a free small tool like XML2PDF
render the PDF perfectly and this, dramatically quicker compare to FOP.
I?ve tried to play with JAVA memory etc? no way.
Thanks and regards
JP
<http://www.mulberrytech.com/xsl/xsl-list>XSL-List info and archive
<-list/554170>EasyUnsubscribe
(<>by email)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--