Tracking down managed memory leaks

Steps to track managed memory leaks

Simple Steps

Very Simple:
1. Debug your code from VS and run.
2. When app is stable, from VS break all (or pause)
3. Now open “Immediate window”
4. Type following to load sos.dll
.load C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\sos.dll
5. Then type
!DumpHeap –type
For Ex:
!DumpHeap -type SomeNameSpace.ClassNameObj
Above command will give reference counts of specified type, along with the address of each reference.
7 Then you can use: !gcroot
For Ex: !gcroot 02bcddc8
This will give the reachable reference path that is holding your reference. Check for HANDLE(Pinned) in above result. This specifies the non collectible references. Others with HANDLE(WeakSh) or HANDLE(WeakLn) are weak short and weak long references that can be collected by garbage collector.

References

Comments

Post a Comment

Popular posts from this blog

C# Polymorphic types conversion with Generics

Image
Polymorphism has been interviewer's  delight for ages. I have been taking interviews for quite some time.  And ever since i started preparing question on C# Polymormism, I have been getting surprises. To prepare interview questions, I try writing code, verify it and and then twist the code snippet to make it "interview-able". This blog is to highlight some of the surprises that i have got while preparing the questions.  The motive of this blog is to highlight tricky points to keep in mind while writing overloaded Functions with Generic parameter. To explain the concept, I'll start with this short code snippet and would like readers to predict the output without scrolling down to answer. Code - 1  If you know the output and the reasoning behind it, then you may leave the rest of blog as you probably are better expert than rest of my audience.  And if you are still read...
Read more

A free roller coaster ride...

Sometimes low and sometimes high, my life these days is on a roller coaster ride. yes indeed, its a roller coaster ride. some friends I had, some of them were my guide, some of whom i kept fighting with, and some of whom I always abide, some kept laughing at me, some made me smile, and some of them were dying to see me die. sometime low and some times high, my life indeed, is on a roller coaster ride. So many promises I have made, not to commit yet another mistake, making mistakes is never missed, the only mistake being kept aside, sometime low and some times high, my life these days is on a roller coaster ride. the unluckiest day recently arrived, that means the luckiest would soon arrive, as i believe it's a roller coaster ride, if it has a low, it must have a high, I am enjoying my life as its a free free free, roller coaster ride. sometimes low, sometimes high, my life indeed, is on a roller coaster ride.
Read more

Data Binding in .net

Image
I have been toying with data binding in .net for quite some time now. And ever since I started working and analyzing the binding support in .net f/w 2.0, I have always been eager to know: What makes WPF data binding so great that Microsoft showcased it as the biggest driver for WPF and MVVM? Even though the data binding existed in .net framework 2.0, why didn't MS pushed for its use as it did for WPF? The INotifyPropertyChanged interface was introduced in .net framework 2.0 and was fully supported by WinForm binding engine. However, most of my fellow developers are unaware of this fact.  So the fundamental question that arise is why should one go for WPF if all we want is nice Data Binding support and it’s available in .net 2.0? The answer to this question is, MS has introduced an all new Data Bindinding engine in WPF which fixes lots of bugs of WinForm data binding, has a much improved performance. And I think this is enough for any GUI developer to consider switching to WPF ...
Read more