To reply to this thread
Re: OutOfMemoryError: Java heap space
Thu, 03 Jul 2014 14:35:00 GMT
to Chandone
For my part, for the same problem, I noticed I had the 32bits version of
JRE. I installed the 64 bits version and no more OutOfMemoyError.
Regards
JP
)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:288)
Any help would be highly appreciated.
Cheers,
Erwann
--
View this message in context:
http://apache-fop.1065347.n5.nabble.com/OutOfMemoryError-Java-heap-space-tp4271p40861.html
Sent from the FOP - Users mailing
As has been said many times on this list, FOP still has some
restrictions concerning the handling of large documents. There are a
bunch of work-arounds, most of them documented on the website and many
of them elaborated on this list.
The long-term solution is to allocate resources to help us
Daniel Noll wrote:
David Delbecq wrote:
Increase memory allocated to java with -Xmx256m
That's an invalid solution for two reasons:
1. Customers who use our application often only have about 256MB maximum
RAM or less, and setting more than that will cause excessive paging
to disk.
May 2006 06:17 AM
To: FOP Users Mailing List
Subject: OutOfMemoryError: Java heap space
Hi, folks.
I am working on improving our application by making it able to cope with
larger text than it can currently handle.
My test document is some 36MB of text, which is really just the same
sentence over
David Delbecq wrote:
Increase memory allocated to java with -Xmx256m
That's an invalid solution for two reasons:
1. Customers who use our application often only have about 256MB maximum
RAM or less, and setting more than that will cause excessive paging
to disk.
2. We're already using
Hi, folks.
I am working on improving our application by making it able to cope with
larger text than it can currently handle.
My test document is some 36MB of text, which is really just the same
sentence over and over. We first generate the document as HTML (for
simpler templating), and
