Hi,

thanks for the response. 

Yes, the memory leak in consitent in each pass ( from step 2 to step 5).  I 
had read an article on the GC of MSXML , but it didnt help much. 

Can you suggest anything else so that the memory leak problem solved. 


-tanish

"Anthony Jones" wrote:

> "Tanish" <Tanish@d...> wrote in message
> news:C0062A7E-AF43-4218-81A7-51E8F3D40528@m......
> > hi ,
> >
> >
> > I am building a VC++  application, in which i am using MSXML 6 parser.
> The
> > problem i am facing the memory consumption by the application. I had
> profiled
> > the application using AQTime and the profiler shows the increase the
> memory
> > consumption by the MSXML6.dll. Once the xml related task is over the
> memory
> > occupied by the application should get release but that does not happen
> and
> > the major part of memory is occupied by the MSXML6.dll .
> >
> > The basic outline of the application:
> >
> > 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.
> >
> >
> > I searched a lot on the net about this problem but couldnt get the correct
> > solution.
> >
> > Can anyone suggest what to do?
> >
> 
> Having got passed step 1 have you tried having your app repeat steps 2 to 5
> several times before closing the app.  Does it "leak memory" by the same
> significant amount on each pass or after the first or second pass does the
> allocated amount of memory stabilise?
> 
> MSXML manages its own heap of memory for collecting nodes, this memory is
> shared by all documents.  It has a form of GC to manage this heap.  It also
> permentantly maintains a name table so if you have wide variety of
> namespaces and element names that can get quite big.
> 
> 
> -- 
> Anthony Jones - MVP ASP/ASP.NET
> 
> 
>