http://blogs.msdn.com/tess/archive/2008/04/21/does-interrupting-gc-waitforpendingfinalizers-interrupt-finalization.aspxI got a question the other day around calling GC.Collect and GC.WaitForPendingFinalizers. The issue revolved around a problem where the finalizer was blocked and where the application would call GC.Collect() and GC.WaitForPendingFinalizers() which thensv-SECommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/tess/archive/2008/04/21/does-interrupting-gc-waitforpendingfinalizers-interrupt-finalization.aspx#8414715Mon, 21 Apr 2008 17:37:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:8414715Sasha Goldshtein<p>This is a classic case of poor documentation. &nbsp;The MSDN doesn't reflect the fact that it's not the GC thread that runs the finalizer... &nbsp;From reading the quote above that's what had me most confused.</p> http://blogs.msdn.com/tess/archive/2008/04/21/does-interrupting-gc-waitforpendingfinalizers-interrupt-finalization.aspx#8414797Mon, 21 Apr 2008 18:16:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8414797Nixta<p>Thanks for that, Tess. Your blog is fantastic and these posts and the labs are fascinating.</p> <p>Oh, how I wish they'd been around a couple of years ago :)</p> <p>All these posts and your help on all the above have finally persuaded me that I need to seriously get to grips with windbg. I'd thought my days of this level of debugging were long gone, but I guess it's time to roll up my sleeves and get stuck in.</p>