The following comment has been added to this issue:
Author: Simon Kitching
Created: Mon, 26 Jul 2004 9:24 PM
Body:
Yes, I can confirm that the problem is fixed in the latest CVS.
Thanks for the quick response!
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/XERCESC-1245?page=comments#action_36884
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1245
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESC-1245
Summary: Memory Leak on Schema Validation Failure
Type: Bug
Status: Resolved
Priority: Major
Resolution: FIXED
Project: Xerces-C++
Components:
Validating Parser (Schema) (Xerces 1.5 or up only)
Versions:
Nightly build (please specify the date)
Assignee:
Reporter: Simon Kitching
Created: Mon, 26 Jul 2004 2:07 AM
Updated: Mon, 26 Jul 2004 9:24 PM
Environment: Linux (Debian Sarge), i686, uniprocessor
Description:
I've got a test harness that loads a schema explicitly, then repeatedly
parses an XML document.
When the XML document is valid according to the schema, all is fine.
I can watch /proc/{pid}/status and the VmSize/VmData fields are steady.
But when it is not valid (ie parse reports a validation error to the
ErrorHandler, which throws an exception), a memory leak occurs. The
VmSize/VmData fields creeps steadily upward as repeated parse-fail cycles occur.
I will attach a test harness that demonstrates this problem.
This problem occurs on both the 2.5.0 release, and the nightly snapshot
xml-xerces_20040725043234.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
