Tom Christian's Blog

So in a previous post, we talked about Understanding when to use a Finalizer in your .NET class so now lets take a look at what the Finalize queue looks like and how to tell if things are bad.

A common problem we see when moving to .NET all revolves around the finalizer.  There are a few reasons that this happens:

We recently had a case where the customer was having performance problems.  They were seeing requests take a few minutes to return and didn’t know what was happening.  So they took some dumps while the problem was happening.  So we ran this dump through DebugDiag using the Crash/Hang script and looked at the output.  The first thing we noticed was this:

So we recently came across an issue where Visual Studio 2005 and 2008 Designers were not respecting assembly binding redirection.

There have been a number of reports of networking issues after installing SP2 for Windows Server 2003.  We now have a fix that will address these.  The errors you may see include:

If you try to make an asynchronous call, you will notice that the thread that executes the call doesn't run under the same account as the thread that called it, assuming you are using impersonation.

So this is a customer situation we found were the customer was getting an System.OutOfMemoryException.  We were able to reproduce this with a console application that just ran:

So here is the scenario.  You open a dump from when you were experiencing a problem and try to run an SOS command and you see: