Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - MSXML and memory leak >Thread Next - RE: MSXML and memory leak RE: MSXML and memory leakTo: NULL Date: 9/3/2008 9:00:00 AM 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. | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
