Sherlane Lam wrote:
1. My FO XSL will create table if the XML has table
data. If the XML has not table data provided, it
will not create table in the output PDF. However,
sometime I find it throws the OutOfMemoryError even
there is no table has to create. Therefore, is there
any other possible issues of FOP may cause this
problem?
There are a few more constructs and usages commonly
causing problems with memory exhaustion.
2. We run our program periodically. We find that
even we are using the same XSL and the same XML,
sometime it will throw this exception but some time it
will generate the PDF normally. We have checked the
environment memory usage and sure that during the
rendering process the environment is silent and nearly
only FOP process exists. We find that the FOP process
normally needs only ~29M memory and can perform
smoothly (we set our max heap size to 512M). However,
sometime it will need extra memory exceeds 512M
dramatically during rendering. In this situation it
will throw the Error.
This is odd: PDF generation should be deterministic, if
it runs ssmoothly once it should run a second time, provided
all the input, including external images, fonts and hyphenation
files are the same. Keep in mind however that JVMs have bugs
too.
More information: the Error is thrown at
at org.apache.fop.fonts.TTFSubSetFile.readFont
This routine had problems with certain Unicode fonts in
0.20.4 (although they should be deterministic too), try
with 0.20.5rc3a.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
