On Jul 29, 2008, at 01:37, Daniel Noll wrote:
Andreas Delmelle wrote:
If FOP itself would unnecessarily hold on to a TTF, then a GC will
not magically release it.
But if it had a FileInputStream (for example) open and forgot to
close it, then the FileInputStream finaliser would close it la
Andreas Delmelle wrote:
If FOP itself would unnecessarily hold on to a TTF, then a GC will not
magically release it.
But if it had a FileInputStream (for example) open and forgot to close
it, then the FileInputStream finaliser would close it later, resulting
in the exact same symptoms reporte
On Jul 28, 2008, at 18:03, Matthieu Siggen wrote:
Hi
FWIW:
While debugging I found out that the fopFactory.newFop call
obtains the
handle. Unfortunately, the handle seems to be arbitrarly
released, ie. a
garbage collection is sometimes necessary to free the handle.
OK, this seems to indi
My fonts are TTF. I tested with Acens.ttf and msgothic.ttf.
Last Friday, I tried the binary installation of 0.95beta without any
improvement. The same issue occured (sorry for not mentionning this
earlier).
Jeremias Maerki-2 wrote:
>
> Can you tell on what kinds of files the handles don't get p
Can you tell on what kinds of files the handles don't get properly
released? PFM, PFB, TTF or something else? Have you tried 0.95beta (or
the https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_95
branch) to see if anything changes? We've had quite a few changes in the
font area for 0.9
Hello,
I have a problem where Fop sometimes keeps an open handle on the fonts given
to the FOUserAgent object. The fonts are defined through the
FOUserAgent.setFontBaseURL method.
My code looks like this:
OutputStream out = //this is some output stream
try{
Source source= message.getInputA
