First rate posting on mem analysis


I was just going through some memory leak information and I stumbled across a newish posting from Tess:


 


http://blogs.msdn.com/tess/archive/2006/03/27/561715.aspx


 


This is a great little article with lots of juicy details very much in the spirit of one I wrote some time ago (http://blogs.msdn.com/ricom/archive/2004/12/10/279612.aspx) only with lots more examples and other goodness thrown in too.


 


I especially like the attention to double checking facts which is often overlooked.  There were potentially several false starts in there but there’s good attention to each them so that we can get to the crux of the real problem.  If you’ve been reading me for a while you’ll know that I’ve been trying to encourage an approach where the early steps in an analysis are to first make sure there is a basic understanding of overall resource usage and only then proceeding with the appropriate detail.   Some really nice work there.


 


Only one problem… now I’m going to have to go read the rest of her postings to find the other gems.  Woe is me J


 


Comments (3)

  1. asqui says:

    Hmmm, interesting — I was just about to complain at you about putting relative links in your blog entry (they don’t work too well when they get syndicated via RSS) but when double-checking that I had my facts straight I noticed a curious thing: The links on your blog are complete; only the ones in the RSS feed are relative.

    How backwards!?

    I guess it must be some munging that the MSDN blog server is doing on your behalf…

  2. ricom says:

    I’ll see if I can have something done about that.  I do try to be careful with the links.

    Thanks for the heads up!

  3. It’s a lost smiley face.