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

[bu...@apache.org]

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=23461>.
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=23461

"Memory leak" in xpath evaluations

           Summary: "Memory leak" in xpath evaluations
           Product: XalanJ2
           Version: 2.5
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: org.apache.xpath
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: t.butcher@elsevier.com


Java heap memory is used up whenever evaluating an xpath expression on a DOM 
Document.

The 'leakage' goes away if the following lines in the constructor  
XPathResultImpl(short type, XObject result, Node contextNode)  
(XPathResultImpl.java) are commented out:

if (((m_resultType == XPathResult.ORDERED_NODE_ITERATOR_TYPE) ||
    (m_resultType == XPathResult.UNORDERED_NODE_ITERATOR_TYPE))&&
    (contextNode instanceof EventTarget)) {
        ((EventTarget)contextNode).addEventListener("MutationEvents",this,true);
}