Strategies For Tracking Down Memory Leaks When You've Done Everything Wrong

Question

My program, alas, has a memory leak somewhere, but I\'ll be damned if I know what it is.

Its job is to read in a bunch of ~2MB files, do some parsing and string repl

Answer 1

The managed debugging add in SoS (Son of Strike) is immensely poweful for tracking down managed memory 'leaks' since they are, by definition discoverable from the gc roots.

It will work in WinDbg or Visual studio (though it is in many respects easier to use in WinDbg)

It is not at all easy to get to grips with. Here is a tutorial

I would second the recommendation to check out Tess Fernandez's blog too.