<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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>Memory Leak with delegates and workflow foundation</title><link>http://msmvps.com/blogs/omar/archive/2009/03/14/memory-leak-with-delegates-and-workflow-foundation.aspx</link><description>Recently after Load Testing my open source project Dropthings , I encountered a lot of memory leak. I found lots of Workflow Instances and Linq Entities were left in memory and never collected. After profiling the web application using .NET Memory Profiler</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Memory Leak with delegates and workflow foundation</title><link>http://msmvps.com/blogs/omar/archive/2009/03/14/memory-leak-with-delegates-and-workflow-foundation.aspx#1731748</link><pubDate>Mon, 12 Oct 2009 01:05:41 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1731748</guid><dc:creator>PimpThisBlog.com</dc:creator><description>&lt;p&gt;Thank you for submitting this cool story - Trackback from PimpThisBlog.com&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1731748" width="1" height="1"&gt;</description></item></channel></rss>