DO NOT REPLY [Bug 23461] - "Memory leak" in xpath evaluations

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23461>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23461

"Memory leak" in xpath evaluations





------- Additional Comments From [EMAIL PROTECTED]  2004-10-21 12:07 -------
Hi,

I am from Sun Microsystems and we are using XALAN for XSL processing. Our
application is apparently observing good heap size increase. Using JProbe
analysis tool, I find couple of objects collecting in xsl processing - 

org.apache.xpath.axes.AxesWalker ->
org.apache.xml.dtm.ref.DTMDefaultBaseTraversers$RootTraverser ->
org.apache.xml.dtm.ref.dom2dt.DOM2DTM -> Vector -> Object[] ->
AttrImpl/ElementImpl etc. 

I am not sure what part of our code would result in that. We are using following
code for XSL transformation - 

      Transformer transformer = null;
      if (xmlDoc == null) {
        throw new XSLProcessingException("XSLProcessor: xmlDoc null");
      }
      if (outputStream == null)
        throw new XSLProcessingException("XSLProcessor: outputStream null");

      try {
        transformer = _templates.newTransformer();
      } catch (TransformerConfigurationException tce) {
        throw new XSLProcessingException("XSLProcessor: transformer could not be
created : "
                                         +tce.getMessage());
      }

      if (transformer == null) {
        throw new XSLProcessingException("XSLProcessor: _transformer null");
      }

      try {
        transformer.transform( new DOMSource(xmlDoc),
                               new StreamResult(outputStream));
      } catch (TransformerException te) {
        throw new XSLProcessingException("XSLProcessor: transform failed ("
                                         +te.getMessage() + ")");
      }
    }
  
I suspect the bug raised here is what is resulting in heap size to increase.
When would we have a fix for this bug. It's quite urgent for us as our
application is released and the problem is reported by a customer.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]