You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2002/02/08 11:49:05 UTC
DO NOT REPLY [Bug 6325] New: -
Memory leak using DOM Parser.
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=6325>.
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=6325
Memory leak using DOM Parser.
Summary: Memory leak using DOM Parser.
Product: Xerces-C++
Version: 1.5.1
Platform: All
OS/Version: All
Status: NEW
Severity: Blocker
Priority: Other
Component: DOM
AssignedTo: xerces-c-dev@xml.apache.org
ReportedBy: lbaylot@axway.com
CC: lbaylot@axway.com
Hi,
My application use Xerces 1.5.1 to parse Xml documents that we read in MQ-
Series (<> 100 000 messages * 20 Ko) and we have some memory leaks in the
parser. But, we use the fonctions XMLPlatformUtils::Initialize() at the
beginning of each message and the fonction XMLPlatformUtils::Terminate(); at
the end of each one.
We have rebuilt xerces 1.5 with BoundChecker and, with your sample DOMPrint,
BoundChecker found some Memory leaks (<> 1Ko). So, for my application, 100 000
messages represents 100Mo of memory which are not liberate.
Thanks,
Lionel BAYLOT
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org