<?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>Finding Memory Leaks in WPF-based applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx</link><description>Last update: Sep, 15th, 2009 There are numbers of blogs that folks wrote about memory leaks in Microsoft .Net Framework managed code and unmanaged code based applications. In this blog I wanted to: Show coding practices that can cause memory leaks which</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Finding Memory Leaks in WPF-based applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#7452944</link><pubDate>Tue, 05 Feb 2008 04:38:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7452944</guid><dc:creator>MSDN Blog Postings  » Finding Memory Leaks in WPF-based applications</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2008/02/04/finding-memory-leaks-in-wpf-based-applications/"&gt;http://msdnrss.thecoderblogs.com/2008/02/04/finding-memory-leaks-in-wpf-based-applications/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Finding memory leaks</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#7532864</link><pubDate>Fri, 08 Feb 2008 06:23:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7532864</guid><dc:creator>Tales from the Smart Client</dc:creator><description>&lt;p&gt;I spent a quite a bit of time late in Blend tracking down memory leaks. Jossef has written the article&lt;/p&gt;
</description></item><item><title>Finding memory leaks</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#7533947</link><pubDate>Fri, 08 Feb 2008 07:34:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7533947</guid><dc:creator>Sparkle bloggers</dc:creator><description>&lt;p&gt;I spent a quite a bit of time late in Blend tracking down memory leaks. Jossef has written the article&lt;/p&gt;
</description></item><item><title>re: Finding Memory Leaks in WPF-based applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#7548491</link><pubDate>Sat, 09 Feb 2008 03:05:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7548491</guid><dc:creator>hasanib</dc:creator><description>&lt;p&gt;I was just bitten by the event handler reference bug where a WPF control was referencing a disposed WinForms Form which caused the WinForm Form to stay around long after it was closed &amp;amp; disposed :^( .&lt;/p&gt;
</description></item><item><title>Avoiding a WPF memory leak with DataBinding (Black Magic)</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#8107854</link><pubDate>Sat, 08 Mar 2008 03:01:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8107854</guid><dc:creator>My Expression</dc:creator><description>&lt;p&gt;A quick note that can save you a lot of pain later: I mentioned a while back that binding to an ObservableCollection&amp;amp;lt;T&amp;amp;gt;&lt;/p&gt;
</description></item><item><title>Avoiding a WPF memory leak with DataBinding (Black Magic)</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#8107983</link><pubDate>Sat, 08 Mar 2008 03:16:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8107983</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;A quick note that can save you a lot of pain later: I mentioned a while back that binding to an ObservableCollection&amp;amp;lt;T&amp;amp;gt;&lt;/p&gt;
</description></item><item><title>Memory Leaks in WPF based applications – Blog Update</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#8459697</link><pubDate>Mon, 05 May 2008 08:36:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8459697</guid><dc:creator>WPF Performance</dc:creator><description>&lt;p&gt;We discovered few other potential memory leaks that WPF based application can encounter so I wanted to&lt;/p&gt;
</description></item><item><title>Photoviewer part 3 – Fixing memory leaks</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9011572</link><pubDate>Wed, 22 Oct 2008 22:32:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9011572</guid><dc:creator>Willem Meints</dc:creator><description>&lt;p&gt;In a comment on part 2 about the photoviewer application Erno pointed out a problem with my photoviewer&lt;/p&gt;
</description></item><item><title>re: Finding Memory Leaks in WPF-based applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9012424</link><pubDate>Thu, 23 Oct 2008 07:27:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9012424</guid><dc:creator>b_grainger</dc:creator><description>&lt;p&gt;I posted a blog entry about diagnostic code that can help identify objects participating in Bindings that might cause leaks: &lt;a rel="nofollow" target="_new" href="http://code.logos.com/blog/2008/10/detecting_bindings_that_should_be_onetime.html"&gt;http://code.logos.com/blog/2008/10/detecting_bindings_that_should_be_onetime.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Memory Leaks Demo &amp; Detection in .NET Application</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9412007</link><pubDate>Wed, 11 Feb 2009 07:36:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9412007</guid><dc:creator>Bill Li</dc:creator><description>&lt;p&gt;Memory leaks are always headache of developers. Do .NET developers no longer bother to worry about memory&lt;/p&gt;
</description></item><item><title>Where's your leak at? [Using WinDbg, SOS, and GCRoot to diagnose a .NET memory leak]</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9471350</link><pubDate>Thu, 12 Mar 2009 08:48:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9471350</guid><dc:creator>Delay's Blog</dc:creator><description>&lt;p&gt;In my last post, I explained how it was possible for &amp;quot;hidden&amp;quot; event handlers to introduce memory leaks&lt;/p&gt;
</description></item><item><title>Finding Managed Memory Leaks in WPF and Silverlight applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9496721</link><pubDate>Sun, 22 Mar 2009 02:12:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9496721</guid><dc:creator>WPF, Silverlight and .NET Musings</dc:creator><description>&lt;p&gt;It's been a while since the last post was online. We have been very busy in working on one of the very&lt;/p&gt;
</description></item><item><title>Memory leak with WPF resources</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9554227</link><pubDate>Fri, 17 Apr 2009 16:36:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9554227</guid><dc:creator>Laurent Kempé</dc:creator><description>&lt;p&gt;I am working for a couple of months now with WPF and MVVM on an a business application using .NET Framework&lt;/p&gt;
</description></item><item><title>re: Finding Memory Leaks in WPF-based applications</title><link>http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx#9921620</link><pubDate>Thu, 12 Nov 2009 23:02:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9921620</guid><dc:creator>Fabrice Marguerie</dc:creator><description>&lt;p&gt;I have published an article about leaks in .NET. It contains a link to this article.&lt;/p&gt;
&lt;p&gt;See &lt;a rel="nofollow" target="_new" href="http://weblogs.asp.net/fmarguerie/archive/2009/11/03/article-detect-avoid-memory-leaks.aspx"&gt;http://weblogs.asp.net/fmarguerie/archive/2009/11/03/article-detect-avoid-memory-leaks.aspx&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>