I'm sorry I haven't had a chance to write much lately because of a lot of different reasons. I moved houses and at the same time I started writing some managed debugging scripts for debugdiag 1.1 to allow it to automatically catch a lot of the issues that I've been writing about before. But... enough with the
Similar Posts
I thought I'd share a support story with you from a very interesting case I have. My customer is running a pretty busy ASP.NET application on an 8-way
I have talked about blocked finalizers before and this issue is a special case of blocked finalizers where we are not really finalizing a .NET object but
Rather than spending a lot of time on explaining the details of the garbage collector, I'll refer you to Maoni's blog for some very interesting reading
In my constant effort to make my job obsolete, I have created an add-in for windbg that automatically checks for hang conditions in a .NET memory dump
