Reviews

The cool thing is that, when you have identified what class type is not released, you can select it in the list and click the 'Class Reference Explorer' or 'Instance List' button to get even more information...It shows a list of each of the instances of that type. It also gives you information about size and how far away it is from the GC Root, if it is a new object and so on. But my personal favorite is the 'Class Reference Explorer', as it is graphical representation that quite clearly indicates why your object is still in memory.

Chris Klug, 59north.com

The user-interface is easy to use and adapt to with lots of visual cues (icons, graphs etc.) and makes using the product seamless. We love the filtering options that really allow us to hone in on particular areas of the code that may need reviewing. The quick view of possible leaky event handlers and disposed but still in memory filters are a godsend!

Thushan Fernando, developerfusion.com

Given the speed with which I could diagnose the above two issues, I was really impressed. I also loved the ability to dig around and see what classes were in use and track through object graphs. To get the same job done with the Microsoft SDK tools I would have to correlate information from WinDBG + SOS and from CLRProfiler. The fact that I could do all this drill down in one tool gave me a huge productivity boost.

Scott Seely, devlicio.us