Kaveh,
I am trying to resolve all outstanding issues for a XalanC v1.11
distribution release. Can you can provide a patch for your
memory leak issue to JIRA XALANC? I will evaluate your issue.
The current stable code for XalanC v1.11 is still the subversion trunk:
http://svn.apache.org/repos/asf/xalan/c/trunk
As you mentioned, look at https://issues.apache.org/jira/browse/XALANC-589
as a coding guide. The notes indicate that the patch has been applied.
I have not confirmed that the issue still exists in the current subversion
trunk.
Please raise a JIRA issue with a new patch if the issue still exists in
the current code.
Sincerely,
Steven J. Hathaway
Xalan Documentation Project
On 8/23/2012 12:48 AM, Kaveh Goudarzi wrote:
Hi All,
We're using Xalanc V1.11 for XPath evaluations with Xerces 3.1.1 and
I'm seeing memory leaks when
XalanSourceTreeParserLiaison.parseXMLStream(MemBufInputSource) is given
an invalid XML to parse. This seems identical to
https://issues.apache.org/jira/browse/XALANC-589. Are there any
patches for the 1.11 source base that one can apply? looking at the
JIRA ticket both the issue and the fix appear to reference version 1.3.x
and looking at svn http://svn.apache.org/repos/asf/xalan/c/tags/ I see
version going up to 1.9 so I'm not sure what is the best way forward.
We're in fact using Xalanc because another library we use has a
dependency on it and so I'm not sure of the impact of upgrading to a
later version of Xalan. I see other memory leaks as well when for
example the XPATH expressions passed to XPathEvaluator.evaluate are
invalid. This is less of an issue as unlike the XML content, we
control the xpath expressions, however we would prefer to switch to a
compatible later version with fixes if possible.
I'm seeing the issue in 32bit windows with VC8 Debug. We've
compiled Xalan and Xerces from sources using the VC8 tool set.
Please let me know if I've missed something obvious.
thanks in advance + kind regards,
Kaveh.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
