I'm loading and parsing a large XML file and it has a horrendous memory leak.
I have run the Desktop Execution Trace Toolkit and cleared up any unclosed references and yet it still persists.
My next plan of attack is to try and understand the allocation and freeing of memory to handles from the report exported from the Desktop Execution Trace Toolkit.
Here's the assumption I'm working on, if a handle has memory allocated but not freed we will get a memory leak.
Am I correct in this assumption and is it a valid place to look?
(I have 600+ instances of this happening on this file)
Lots of Love
Steve