XSLTC: Apparent memory issue/bug? 2003-02-20 - By Santiago Pericas-Geertsen
----- Original Message -----
From: "Mark Brunkhart" <mark@(protected)>
> ...
> At first, I thought it was a problem with the nodeset function, but after
> trying to isolate the bug, it appears to go away when I eliminate some
> imported templates. I've actually created a test case where I can
> eliminate the problem by removing 3 lines of meaningless code (creation of
> an empty variable) that appear _after_ the code above. In other words,
> template code is altering the results of code which is executed before it.
>
If you have a stylesheet that you can use to reproduce this problem, please
file a bug here:
http://nagoya.apache.org/bugzilla/
> I noticed that there is some discussion of a 64K limit (wow that's small)
The limit is on the size of method, not on the stack or the heap. Besides,
this is a compile-time error, so if you're able to run your stylesheet,
you're not reaching this limit.
> that gets overwhelmed when XSL templates are inlined during compilation.
> This seems relevant; however, I've also found two conflicting mentions of
> this on xml.apache.org, one which says that inlining is "on" by default
and
> the other which says it is "off".
In the latest version, inlining is "off" by default (thus, each template
gets generated into a separate method). But as I said, this is inlikely to
be your problem.
Hope this helps.
-- Santiago
|
|
