I also notice a large leak in my program. has anyone found a solution?

I have a simple XML DOM class -

CComPtr< IXMLDOMDocument > m_pDOMDoc; // variable defined in header file

m_pDOMDoc.CoCreateInstance( __uuidof( DOMDocument), NULL, 
CLSCTX_INPROC_SERVER); // called in the constructor
..
m_pDOMDoc->load // used in one of the methods

I do not see memory being released after the destructor is called. What 
should I do to make sure that memory gets released?


"Darren Morby" wrote:

> I have a similar problem with MSXML 4.0 SP2.
> 
> My problem is that MSXML is not only allocating large objects in heap 
> memory, MSXML is allocating large heaps and not destroying them.  Is that 
> what you were seeing in your app as well?
> 
> -- Darren --
> 
> "Tanish" wrote:
> 
> > 1. Starts the application ( average memory consumption at this stage is ~20MB)
> > 2. Starts a new thread ( for handling the XML function)
> > 3. Initializes the IXMLDOMDocument.
> > 4. Performs the xml related operations ( loading, reading- writing , saving 
> > the xml file )
> > ( When the application is in stage 4 ( mentioned above ) the memory 
> > consumtion continuously increases.)
> > 5. Once the required xml task is over , releases the xmldomdocument 
> > objectthe thread exits but still the memory consumtion is same.
> > 6. The memory is released only after the application is closed.
>