ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak

ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leakhttp://blogs.iis.net/tomchris/archive/2008/04/22/asp-net-tips-how-to-identify-a-com-call-that-is-blocking-gc-causing-a-memory-leak.aspxProblem Description So this is a customer situation we found were the customer was getting an System.OutOfMemoryException.  We were able to reproduce this with a console application that just ran: For Iterator = 0 To 99999999999 Regex.IsMatch(CONNECTION_STRINGenCommunityServer 2007 SP1 (Build: 20510.895)ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak - Tom Christian's Bloghttp://blogs.iis.net/tomchris/archive/2008/04/22/asp-net-tips-how-to-identify-a-com-call-that-is-blocking-gc-causing-a-memory-leak.aspx#2314143Tue, 22 Apr 2008 17:08:36 GMT50bcf3b4-f6fe-4638-adff-0c150e922e99:2314143ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak - Tom Christian's Blog<p>Pingback from  ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak - Tom Christian&#39;s Blog</p> <img src="http://blogs.iis.net/aggbug.aspx?PostID=2314143" width="1" height="1">