<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>ASP.NET Tips: Looking at the finalization queue</title><link>http://blogs.msdn.com/tom/archive/2008/04/28/asp-net-tips-looking-at-the-finalization-queue.aspx</link><description>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. The command we use is !finalizequeue in sos: 0:010&amp;gt; !finalizequeue</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>ASP.NET Tips: Looking at the finalization queue</title><link>http://blogs.msdn.com/tom/archive/2008/04/28/asp-net-tips-looking-at-the-finalization-queue.aspx#8435640</link><pubDate>Mon, 28 Apr 2008 19:13:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8435640</guid><dc:creator>DotNetKicks.com</dc:creator><description>&lt;p&gt;You've been kicked (a good thing) - Trackback from DotNetKicks.com&lt;/p&gt;
</description></item><item><title>Looking at the finalization queue in the debugger</title><link>http://blogs.msdn.com/tom/archive/2008/04/28/asp-net-tips-looking-at-the-finalization-queue.aspx#8435646</link><pubDate>Mon, 28 Apr 2008 19:17:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8435646</guid><dc:creator>Useful IIS/ASP.NET Information provided by Microsoft Support Teams</dc:creator><description>&lt;p&gt;Want to see what objects you have added a finalizer too, follow the information here .&lt;/p&gt;
</description></item><item><title>re: ASP.NET Tips: Looking at the finalization queue</title><link>http://blogs.msdn.com/tom/archive/2008/04/28/asp-net-tips-looking-at-the-finalization-queue.aspx#9930820</link><pubDate>Tue, 01 Dec 2009 15:52:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9930820</guid><dc:creator>Nariman</dc:creator><description>&lt;p&gt;Hi there; I think it's a mistake to suggest that GC.SuppressFinalize will 'remove' the object from the !finalizequeue in SOS - that you still see Systme.Data.DataTables (which call GC.SuppressFinalize) in their constructors is perfect evidence of this. Calling SuppressFinalize will prevent the promotion to FReachable and allow the object to be reclaimed on the first GC pass (just as non-finalizable objects would) but it will still list under this output. As such, this command in and of itself isn't very useful: a command in the *public* SOS that works for 2.x assemblies that shows FReachable or the Finalization Queue (where the bit in the header for finalization-requires is still set to ON) would help.&lt;/p&gt;
&lt;p&gt;[1]-&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.devnewsgroups.net/dotnetframework/t19821-finalize-queue-windbg-sos.aspx"&gt;http://www.devnewsgroups.net/dotnetframework/t19821-finalize-queue-windbg-sos.aspx&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: ASP.NET Tips: Looking at the finalization queue</title><link>http://blogs.msdn.com/tom/archive/2008/04/28/asp-net-tips-looking-at-the-finalization-queue.aspx#9930867</link><pubDate>Tue, 01 Dec 2009 17:01:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9930867</guid><dc:creator>Tom</dc:creator><description>&lt;p&gt;Excellent point Nariman. &amp;nbsp;I am updating the post to reflect that difference.&lt;/p&gt;
</description></item></channel></rss>