Home › Blogs › Tom Christian's Blog › 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 leak

Posted: Apr 22, 2008 1 comments

Average Rating

Tags: ASP.NET; ASP.NET Tip; Debugging; High Memory; IIS

Email this Post
DotNetKicks
Digg
Facebook
Del.icio.us

Tom Christian's Blog RSS

Important blogs to visit...
Microsoft Optimization...
Any other .NET 3.5 SP1...

Problem 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_STRING Read More...

Read the complete post here

Comments

Submit a Comment

Plain text is accepted.
URLs starting with http:// are converted to links.You are logged in as
Anonymous