This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I haven't had any memory leak problems reported for a long while. But they are always possible: and not easy to debug. You may need to get hold of a Java monitoring tool to find out which created objects are accumulating. It's best to raise this on the saxon-help list at http://saxon.sourceforge.net/ Mike Kay Software AG > -----Original Message----- > From: owner-xsl-list@lists.mulberrytech.com > [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Paul Brown > Sent: 19 July 2001 22:23 > To: xsl-list@lists.mulberrytech.com > Subject: [xsl] issues with Saxon TRAX support? > > > > 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. > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |