<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/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/" xmlns:cs="http://blogs.iis.net/"><channel><title>Tom Christian&amp;#39;s Blog : Crash</title><link>http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx</link><description>Tags: Crash</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>ASP.NET Tip: How to avoid creating a GC Hole</title><link>http://blogs.iis.net/tomchris/archive/2008/09/25/asp-net-tip-how-to-avoid-creating-a-gc-hole.aspx</link><pubDate>Thu, 25 Sep 2008 10:00:00 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2645478</guid><dc:creator>ASP.NET Debugging : IIS</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/tomchris/rsscomments.aspx?PostID=2645478</wfw:commentRss><comments>http://blogs.iis.net/tomchris/archive/2008/09/25/asp-net-tip-how-to-avoid-creating-a-gc-hole.aspx#comments</comments><description>There are only a few things that can make a .NET process crash.&amp;#160; The most common one is an Unhandled Exception getting raised.&amp;#160; Another way that is can happen is by creating a GC Hole. What is a GC Hole So first a little background on what I...(&lt;a href="http://blogs.iis.net/tomchris/archive/2008/09/25/asp-net-tip-how-to-avoid-creating-a-gc-hole.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2645478" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/tomchris/archive/tags/Debugging/default.aspx">Debugging</category><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.iis.net/tomchris/archive/tags/.NET/default.aspx">.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx">Crash</category></item><item><title>ASP.NET and Performance</title><link>http://blogs.iis.net/tomchris/archive/2008/06/23/asp-net-and-performance.aspx</link><pubDate>Mon, 23 Jun 2008 18:29:34 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2441561</guid><dc:creator>ASP.NET Debugging : IIS</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/tomchris/rsscomments.aspx?PostID=2441561</wfw:commentRss><comments>http://blogs.iis.net/tomchris/archive/2008/06/23/asp-net-and-performance.aspx#comments</comments><description>I wanted to talk about monitoring performance in ASP.NET for a bit.&amp;#160; I have already posted a few postings that talk around this issue, namely: ASP.NET Debugging - High Memory part 5 – Fragmentation ASP.NET Debugging - ASP.NET Tips- How to use DebugDiag...(&lt;a href="http://blogs.iis.net/tomchris/archive/2008/06/23/asp-net-and-performance.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2441561" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET+Tip/default.aspx">ASP.NET Tip</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Debugging/default.aspx">Debugging</category><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.iis.net/tomchris/archive/tags/.NET/default.aspx">.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Microsoft/default.aspx">Microsoft</category><category domain="http://blogs.iis.net/tomchris/archive/tags/High+Memory/default.aspx">High Memory</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Hang/default.aspx">Hang</category><category domain="http://blogs.iis.net/tomchris/archive/tags/High+CPU/default.aspx">High CPU</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx">Crash</category></item><item><title>ASP.NET Tips: What to gather to troubleshoot</title><link>http://blogs.iis.net/tomchris/archive/2008/05/21/asp-net-tips-what-to-gather-to-troubleshoot.aspx</link><pubDate>Wed, 21 May 2008 15:38:59 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2372309</guid><dc:creator>ASP.NET Debugging : IIS</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/tomchris/rsscomments.aspx?PostID=2372309</wfw:commentRss><comments>http://blogs.iis.net/tomchris/archive/2008/05/21/asp-net-tips-what-to-gather-to-troubleshoot.aspx#comments</comments><description>So now that I am done with all the individual posts, I thought I would wrap them all together.&amp;#160; So here are all of the posts that I created on gathering information when you are having a problem. Please keep in mind that these are geared towards...(&lt;a href="http://blogs.iis.net/tomchris/archive/2008/05/21/asp-net-tips-what-to-gather-to-troubleshoot.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2372309" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET+Tip/default.aspx">ASP.NET Tip</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Debugging/default.aspx">Debugging</category><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.iis.net/tomchris/archive/tags/.NET/default.aspx">.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/High+Memory/default.aspx">High Memory</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Hang/default.aspx">Hang</category><category domain="http://blogs.iis.net/tomchris/archive/tags/High+CPU/default.aspx">High CPU</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx">Crash</category></item><item><title>ASP.NET Tips: What to gather to troubleshoot - part 6 - Recycle due to memoryLimit</title><link>http://blogs.iis.net/tomchris/archive/2008/05/20/asp-net-tips-what-to-gather-to-troubleshoot-part-6-recycle-due-to-memorylimit.aspx</link><pubDate>Tue, 20 May 2008 16:03:04 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2369360</guid><dc:creator>ASP.NET Debugging : IIS</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/tomchris/rsscomments.aspx?PostID=2369360</wfw:commentRss><comments>http://blogs.iis.net/tomchris/archive/2008/05/20/asp-net-tips-what-to-gather-to-troubleshoot-part-6-recycle-due-to-memorylimit.aspx#comments</comments><description>Here is another situation that you may come across and what to do in order to gather information about it. The following steps will configure DebugDiag to automatically capture a memory dump of the ASPNET_WP.exe process recycling when it exceeds the memoryLimit...(&lt;a href="http://blogs.iis.net/tomchris/archive/2008/05/20/asp-net-tips-what-to-gather-to-troubleshoot-part-6-recycle-due-to-memorylimit.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2369360" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET+Tip/default.aspx">ASP.NET Tip</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Debugging/default.aspx">Debugging</category><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.iis.net/tomchris/archive/tags/.NET/default.aspx">.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/High+Memory/default.aspx">High Memory</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx">Crash</category></item><item><title>ASP.NET Tips: What to gather to troubleshoot – part 3 – Crash</title><link>http://blogs.iis.net/tomchris/archive/2008/05/06/asp-net-tips-what-to-gather-to-troubleshoot-part-3-crash.aspx</link><pubDate>Tue, 06 May 2008 15:39:51 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2341286</guid><dc:creator>ASP.NET Debugging : IIS</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/tomchris/rsscomments.aspx?PostID=2341286</wfw:commentRss><comments>http://blogs.iis.net/tomchris/archive/2008/05/06/asp-net-tips-what-to-gather-to-troubleshoot-part-3-crash.aspx#comments</comments><description>Defining an IIS Crash A Crash in IIS occurs when an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) terminates unexpectedly. A Crash typically happens when there is an Unhandled Exception caused by an Access Violation, Stack Overflow, etc. In these...(&lt;a href="http://blogs.iis.net/tomchris/archive/2008/05/06/asp-net-tips-what-to-gather-to-troubleshoot-part-3-crash.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2341286" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET+Tip/default.aspx">ASP.NET Tip</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Debugging/default.aspx">Debugging</category><category domain="http://blogs.iis.net/tomchris/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.iis.net/tomchris/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.iis.net/tomchris/archive/tags/Crash/default.aspx">Crash</category></item></channel></rss>