[ http://issues.apache.org/jira/browse/XALANJ-1673?page=all ]
Brian Minchau updated XALANJ-1673:
----------------------------------
Version: Latest Development Code
(was: 2.5)
> "Memory leak" in xpath evaluations
> ----------------------------------
>
> Key: XALANJ-1673
> URL: http://issues.apache.org/jira/browse/XALANJ-1673
> Project: XalanJ2
> Type: Bug
> Components: XPath
> Versions: Latest Development Code
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Tim Butcher
> Assignee: Xalan Developers Mailing List
>
> 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);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
