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 2003/08/06 12:49:23 UTC
DO NOT REPLY [Bug 22168] New: -
memory not releaser by DOMParser
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=22168>.
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=22168
memory not releaser by DOMParser
Summary: memory not releaser by DOMParser
Product: Xerces-C++
Version: 2.3.0
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: DOM
AssignedTo: xerces-c-dev@xml.apache.org
ReportedBy: julien.delsuc@gemplus.com
I am using the deprecated version of DOM ( because I upgraded an old program of
mine ).
I wrote a MemoryManager to trace all allocations and deallocations made my xerces.
The result is that many allocated memory is never deallocated ?
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
memory not releaser by DOMParser
Posted by Peter Guyatt <pg...@telesoft-technologies.com>.
Hi,
Are you actually calling the parser.resetDocumentPool() method.
This will delete all of the DOM trees that has been build up, since every
time you call the DOMParser.parse method it adds the new DOM tree to an
internal vector.
Thanks
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org