(X) Hide this Watch the recording of the latest SilverlightShow webcast 'Running Silverlight Outside the Browser and with Elevated Trust'.
Join our next live webinar session by Braulio Diez - Sketchflow in Real Scenarios, on Sept 29th, 8am - 9am PDT.
Learn More | Sign Up | More Webinars by SilverlightShow


Skip Navigation LinksHome / News / View News

Using WinDbg, SOS, and GCRoot to diagnose a .NET memory leak

+ Add to SilverlightShow Favorites
0 comments   /   posted by Silverlight Show on Mar 13, 2009
(0 votes)
Tags: .NET , Issues , Solutions

In his last post, David Anson explained how it was possible for "hidden" event handlers to introduce memory leaks and showed an easy way to prevent such leaks. Now he is going to show how to diagnose a .NET memory leak with the help of WinDbg, SOS, and GCRoot.

What if you don't know the source of the memory leak in the first place? Knowing how something is leaking is the first step to fixing it, and the web has some great resources for learning more about tracking down managed memory leaks in WPF and Silverlight applications. I am not going to try to duplicate that information here. :) Instead, I'll refer interested readers to these excellent resources and recommend a bit of web searching if additional background is needed.



Comments RSS RSS
No comments

Add Comment


Please add 4 and 5 and type the answer here: