I like FOP 1.1 a lot: Unlike previous versions, it tells you which page
it's processing, which can make debugging easier, and also it gives you
that warm fuzzy feeling that you're somewhat in control of things. :-)
However, with really big books, I'm hitting a wall, like this:
Okt 24, 2012 8:21:16 PM org.apache.fop.events.LoggingEventListener
processEvent
INFO: Rendered page #2630.
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit
exceeded
That is, FOP stops at about 2600 pages with an out of memory error. On
Stackoverflow (http://preview.tinyurl.com/94qute5), there's an
indication why this happens:
"This message means that for some reason the garbage collector is taking
an excessive amount of time (by default 98% of all CPU time of the
process) and recovers very little memory in each run (by default 2% of
the heap).
This effectively means that your program stops doing any progress and is
busy running only the garbage collection at all time."
Does this mean it's a FOP 1.1 bug, or would there be anything I could do
to give it/Java more memory and prevent it from failing?
The error happens on an 8 GB RAM 4-core machine. At the time FOP ended,
there was like 2 GB RAM left.
--
Cheers,
Stefan Hinz <stefan.h...@oracle.com>, MySQL Documentation Manager
Phone: +49-30-82702940, Fax: +49-30-82702941, http://dev.mysql.com/doc
ORACLE Deutschland B.V.& Co. KG
Registered Office: Riesstr. 25, 80992 Muenchen, Germany
Commercial Register: Local Court Of Munich, HRA 95603
Managing Director: Jürgen Kunz
General Partner: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Register Of Chamber Of Commerce: Midden-Niederlande, No. 30143697
Managing Directors: Alexander van der Ven, Astrid Kepper, Val Maher
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
