<?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 Case Study: Tracing your way to Out Of Memory Exceptions</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx</link><description>One of my colleagues asked me to look at a memory dump for a customer and I thought that was I found was fairly interesting so here is the story. Problem description: Memory in our ASP.NET application (w3wp.exe) keeps growing and growing and requests</description><dc:language>sv-SE</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: ASP.NET Case Study: Tracing your way to Out Of Memory Exceptions</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx#2860720</link><pubDate>Fri, 25 May 2007 07:58:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2860720</guid><dc:creator>paul b</dc:creator><description>&lt;p&gt; Tess - &amp;nbsp;Thanks very much for all your useful posts. I have learned many things from them.&lt;/p&gt;
&lt;p&gt;Is there anyway to get some of this information listed above (mainly starting address of the heaps as shown) but through some API call? It would be great to get this dynamically if possible. Thanks&lt;/p&gt;</description></item><item><title>re: ASP.NET Case Study: Tracing your way to Out Of Memory Exceptions</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx#3425222</link><pubDate>Wed, 20 Jun 2007 17:26:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3425222</guid><dc:creator>bug0r</dc:creator><description>&lt;p&gt;Wow, it's really my case.&lt;/p&gt;
&lt;p&gt;Thank you very much.&lt;/p&gt;</description></item><item><title>top 10 windbg.exe usage articles</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx#3504708</link><pubDate>Mon, 25 Jun 2007 00:10:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3504708</guid><dc:creator>roy ashbrook</dc:creator><description>&lt;p&gt;These are the articles (in no particular order) that I felt best showed a thorough use of the windbg&lt;/p&gt;</description></item><item><title>re: ASP.NET Case Study: Tracing your way to Out Of Memory Exceptions</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx#8083753</link><pubDate>Fri, 07 Mar 2008 05:00:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8083753</guid><dc:creator>dgartner</dc:creator><description>&lt;p&gt;I'm debugging this same issue. &amp;nbsp;You page is the first to come up when I google System.Web.Util.Profiler. &amp;nbsp;Thanks for this!&lt;/p&gt;</description></item><item><title>Troubleshooting a performance issue with Failed Request Tracing and appcmd in IIS7</title><link>http://blogs.msdn.com/tess/archive/2007/03/15/asp-net-case-study-tracing-your-way-to-out-of-memory-exceptions.aspx#8878564</link><pubDate>Tue, 19 Aug 2008 15:04:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8878564</guid><dc:creator>If broken it is, fix it you should</dc:creator><description>&lt;p&gt;I know I'm a little late in the game, but I decided that after vacation it was finally time for me to&lt;/p&gt;
</description></item></channel></rss>