Is it an actual out-of-memory problem, or a resource limitation problem of
one sort or the other?
As an experement, if you're just trying to get the thing processed, try
using <xsl:strip-space elements="*"/>
The only other suggestions I can offer are 1) try the latest CVS source, or
2) send me (privately) the input file and the XSLT, and I will try running
it on my end. I am also working on a optimization branch right now, and it
would be interesting to see if the behavior is any different, or if there's
something that could be rearchitected to help.
But, out of 500Mb, it might be that we simply can't handle it without Joe's
pruning code (or at least tail pruning) being operational (work on which
keeps getting pushed back in favor of other priorities... ugh.)
-scott
Morten
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
k> cc: (bcc: Scott Boag/CAM/Lotus)
Subject: Re: Dealing with
java.lang.OutOfMemoryError
01/31/2002
01:02 PM
[EMAIL PROTECTED] wrote:
> Which version are you working with?
Xalan 2.2.14. The error puzzles me, I work in few levels
of the document, and would expect a steady memory usage
when using SAX.
Morten
