You can’t have leaks in managed code, right? Ah, but you can, in interesting and subtle ways. In this session, we’ll look at how you can have a leak in managed code, how to find leaks using WinDbg, and some ways to prevent leaking in the first place.
Slides
Resouce Links:
WinDbg Download: http://www.microsoft.com/whdc/devtools/debugging/default.mspx
My “Getting Started” blog post: http://erickepes.com/2009/11/21/obtaining-a-memory-dump-to-diagnose-memory-leaks/
SOS Debugging Extension: http://msdn.microsoft.com/en-us/library/bb190764.aspx
Brock Reeve’s sample code (what I used in the demo): http://brockreeve.com/post/2010/02/10/Windbg-and-SOS-for-Visual-Studio-NET-Weenies.aspx
Tess Ferrandez’s blog (lots of good stuff): http://blogs.msdn.com/b/tess/
Other interesting links:
