Wednesday July 29th

Tuesday July 28th

2 Kicks

Is That a WeakReference In Your Gen 2 or Are You Just Glad to See Me?

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.

2 comments

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?

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network