DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9509>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9509 Inconsistent exception when XSL runs into an infinite loop ------- Additional Comments From [EMAIL PROTECTED] 2002-05-30 13:28 ------- Re different results each time in your test: GC is somewhat probabilistic in many VMs, and finalizers can further complicate matters, so I'm not shocked that a second out-of-memory failed in a different place. Memory shortages can cause many Java operations to fail, and I suspect that unless everyone in both the JDK team and the Xalan team has been _extremely_ careful they won't all yeild the same top-level exception. Re setRecursionLimit: The test for this (examining m_stackGuard in TransformerImpl.executeChildTemplates) appears to be disabled. I believe that's because the old version of StackGuard, with its attempts to check depth of specific recursion loops, was a performance problem. A raw "if it's more than N templates deep it's probably a problem" counter might be worth re-introducing, so users can get a more predictable error response and (possibly) get it sooner. Of course it then becomes the user's responsibility to tune this parameter so it permits enough recursion for all normal executions of that stylesheet.
