On Sep 24, 2008, at 11:39, ACHA | Marco Wayop wrote:
Is there an indication, for example, that the second or third time
around, you end up with
200-300MB of heap that cannot be released? (which would be
indicative of a true memory-leak)
Yes, with every run - eventually - 100MB is added to the tenured
generation and stays there.
That's strange, but may be explained somehow by the fact that the
SAXParser (which references the FOTreeBuilder etc.) remains
referenced in Tomcat's table of ThreadLocals (as can be seen from the
profile output you posted earlier).
As noted, I don't really know what makes Tomcat cleanup that table.
I'm certain that it is unrelated to standard Garbage Collection; as
long as that table holds a hard reference to the SAXParser, the GC
will obviously not magically release it... The best we can do on our
end, is try to make sure FOP holds no dangling references. The change
I committed should hardly make a difference in normal circumstances
(if the context does not keep a hard reference to the SAXParser any
longer than necessary).
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
