From: Michael Kay <mhkay@ic...> - 2001-07-24 07:42:31
I don't know of any memory leak problems in recent Saxon releases. It's
always possible, of course - but it's also possible that it's a problem in
your application. To track it down, it will probably be necessary to use a
Java profiling package of some kind, to see which objects are accumulating
and not being garbage-collected.
> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...]On Behalf Of Paul Brown
> Sent: 23 July 2001 22:40
> To: saxon-help@...
> Subject: [saxon] memory leak in 6.4 / TRAX support issues?
> Are there any known issues with Saxon 6.4's TRAX support?
> Running SAXSource
> (custom, not an XML parser) -> Transformer -> SAXResult
> (org.xml.sax.helpers.DefaultHandler) with a Transformer
> generated from a
> compiled Templates object results in a memory overflow after
> about 10,000
> iterations of the same transformation.
> The code runs without issue through XalanJ2.2.D6.
> -- Paul
> PS FWIW, the two processors are comparable (+/-5%) in speed for my
> applications so far.
> saxon-help mailing list