Yes, Rob has reproduced it. My theory right now is that the recursive
includes in docbook are causing multiple parsers to be created, since the
parser is not reentrant, and the parsers are likely to have some big
tables. Rob said that he could run docbook files by boosting the memory in
the vm.
We have this posted as an SPR (Software Problem Report), but it will take
some time to resolve.
Xerces folks: the problem is that I'm handling xsl:include while I'm in the
middle of a SAX parse, and I don't think the currently executing parser is
reentrant at that point. Do you have any ideas on how this might be
resolved?
The other thing I might be able to try is to post a stack of the
xsl:includes and xsl:imports as the processing occurs, and then process
those stylesheets after the primary parse is completed... i.e. try to build
the stylesheets sequentially, instead of recursivly. I'll have to look
into how feasible this is.
-scott
Steve Fisher
<[EMAIL PROTECTED] To: Scott Boag/CAM/Lotus
<[EMAIL PROTECTED]>
l.ac.uk> cc:
Subject: Re: xalan crashes with
docbook
01/20/00
01:16 PM
On Fri, 14 Jan 2000, Scott Boag/CAM/Lotus wrote:
>
> OK, I'll take a look at this. I wasn't aware of any problems with
docbook.
> The error is occuring during the build of the stylesheet, and looks to be
a
> genuine out of memory error, so I'm a bit surprised.
>
> -scott
>
> Steve Fisher
> <[EMAIL PROTECTED] To: xalan-dev@xml.apache.org
> l.ac.uk> cc: (bcc: Scott
Boag/CAM/Lotus)
> Subject: xalan crashes with
docbook
> 01/14/00
> 02:28 PM
Did you get anywhere with this out of memory condition? - can you
reproduce the error?
Steve
