[ http://issues.apache.org/jira/browse/XERCESC-971?page=comments#action_12315899 ]
Pieter Janse van Rensburg commented on XERCESC-971: --------------------------------------------------- Hi, I am running the DOMPrint example of Xerces 2.6.0 provided, using my own Memory Manager. I also track all allocations and deallocations made by the XercesDOMParser during the parse process. I found that even after calling the resetDocumentPool method on the parser object, there are still some memory segments not released. These segments are only released after deleting the parser object itself. Are there some other methods that can be called to release these segments of memory, say in the case when the parser object is to be reused for parsing multiple xml files? Thanks Pieter > memory not releaser by DOMParser > -------------------------------- > > Key: XERCESC-971 > URL: http://issues.apache.org/jira/browse/XERCESC-971 > Project: Xerces-C++ > Type: Bug > Components: DOM > Versions: 2.3.0 > Environment: Operating System: Windows NT/2K > Platform: PC > Reporter: Julien DELSUC > Assignee: Xerces-C Developers Mailing List > > 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 ? -- 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]
