Today while helping my colleague AnilKP to debug a memory leak issue for w3wp.exe. It was the perfect example to demonstrate scenario where memory leaks were self induced. Here is the complete saga

End customer complained that they had noticed worker process(w3wp.exe) hogs lots of memory. They have notices 1.2 GB process size in the task manager.

Time to look into the w3wp.exe dumps in windbg

http://www.asprangers.com/post/2012/04/03/Beware-Tracing-in-ASPNET-can-lead-to-Memory-leaks-eventually-OOM.aspx

 

Read More