|
Hi Mehdi,
As for your FO, you need to provide a little more
information:
1) Tables in the FO tend to consume quite a lot of memory,
especially when they span multiple pages, are you using them for
laying out the documents?
No, but we have many loooong tables in that huge (5,742 pages) MySQL
5.5 Manual. Some of them have overflow issues (table columns
overlapping), which might add to the problem I was facing.
2) Fonts take up more room than they really should; are you
using custom fonts? Are you embedding fonts?
No, nothing.
Those are the usual culprits that come to mind (though others
may wish to add to them), if you can upload the FO, then someone
will take a look at it.
Should I still do that? As said in the previous reply to Luis and
Glenn, I was able to overcome the build failure with -Xmx4096m and
-nocs. Maybe, as a rule of thumb, give FOP 1 GB per 1000 pages? :-)
Thanks again for FOP 1.1 -- it seems to be a heck of a lot quicker
than FOP 1.0!
Cheers,
Stefan
Hope that helps,
Mehdi
On 24 October 2012 19:49, Stefan
Hinz <[email protected]>
wrote:
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 <[email protected]>,
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: [email protected]
For additional commands, e-mail: [email protected]
--
Cheers,
Stefan Hinz <[email protected]>, 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: [email protected]
For additional commands, e-mail: [email protected]
|
