If broken it is, fix it you should

Using the powers of the debugger to solve the problems of the world - and a bag of chips    by Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft)

February, 2009

  • If broken it is, fix it you should

    .NET Memory Leak reader email: Are you really “leaking” .net memory

    I get several emails every week through the blog asking for help on various issues.  Unfortunately due to time constraints I can’t really look at them all on an individual bases but I thought this particular request might be interesting to share. The problem description was “One of our w3wp.exe’s just keep on growing (slowly), and never releasing memory back to the pot.  The main offender appears to be System.String and System.Object[]”  and the email then had some !dumpheap –stat...
  • If broken it is, fix it you should

    .NET Memory Leak: To dispose or not to dispose, that’s the 1 GB question

    I was looking at a memory dump recently for an issue where the process would grow to over 1 GB and return OutOfMemory Exceptions. Debugging the issue: A full user dump of the w3wp.exe process was taken with debug diag 1.1 when memory was really high. If you are reading this and have no clue what debug diag is, how to get dumps with it, or use leak tracking, here is the download and the usage instructions . The dump itself was 1.34 GB which is basically the memory we have committed (used) so it was...
Page 1 of 1 (2 items)