Memory Leaks in MSXML ?
-
Ihave a COM method which has Input,Outout as XML, It includes loading a string in to XMLDOM and processing on the nodes. i have used memory leak article on CP to find the MemoryLeak http://www.codeproject.com/tools/leakfinder.asp[^] from my observation and some reading on google, it seems that Release() and LoadXML are two methods which seems to have some memory leak, but i simply could not find the work arround, i have also gone through the "Delayed Clean up mechanism" but again without solution to my problem big problem is as the output XML grows there is more wastage of memory, as this method is called arround ~4200 time a day the resultant is mess If this is a repost kindly redirect(as of now i can see only one post in the XML section)er to question !
Chase your dreams ! http://eminencetech.net[^]
-
Ihave a COM method which has Input,Outout as XML, It includes loading a string in to XMLDOM and processing on the nodes. i have used memory leak article on CP to find the MemoryLeak http://www.codeproject.com/tools/leakfinder.asp[^] from my observation and some reading on google, it seems that Release() and LoadXML are two methods which seems to have some memory leak, but i simply could not find the work arround, i have also gone through the "Delayed Clean up mechanism" but again without solution to my problem big problem is as the output XML grows there is more wastage of memory, as this method is called arround ~4200 time a day the resultant is mess If this is a repost kindly redirect(as of now i can see only one post in the XML section)er to question !
Chase your dreams ! http://eminencetech.net[^]
I hope its not a memory leak its catching... Caching Caching situations will usually show up as leaks in leakdiag because they are allocations that have not been freed. In some situations, it is possible to prevent false positives by disabling caching. Otherwise, it would require a code review to identify the allocations are actually being cached for later reuse. If the leaks are showing up in specific allocators, then tracking only that allocator will prevent caching from appearing to be a leak since LeakDiag will tracke the originating allocation call instead of the underlying heap or virtual alloc calls which might be cached by the component. The COM allocator is one example of an allocator that can be used to prevent false leaks due to caching.
Regards Anil