John Robbins walks us through debugging an application which is not clearing its memory during garbage collection due to WeakReferences. He shows us how to use the tools available to us to trace the memory problem all the way back to the source.
Memory leaks are tough to track down. There are other profilers like ANTS which are easier to use.
This is strange... I don't quite get it. Surely WeakReferences only encourage/ensure earlier garbage collection? How can they create memory leaks?