Thursday, September 30, 2004

.NET Memory Profiler - Find Memory Leaks and Optimize Memory Usage in Programs Written in C#, VB.NET or any other .NET Language

.NET Memory Profiler - Find Memory Leaks and Optimize Memory Usage in Programs Written in C#, VB.NET or any other .NET Language

"NET Memory Profiler is a powerful tool for finding memory leaks and optimizing the memory usage in programs written in C#, VB.NET or any other .NET Language.

It allows you to retrieve information about all instance allocations performed on the garbage collected heap (GC heap) and all instances that reside on the GC heap. The retrieved information is presented in real-time, both numerically and graphically.

Information is provided about: all classes, all instances of classes, the call stacks of the instance allocations, the path to a root from each instance.

The profiler also contains a dispose tracker, which provides additional data about disposable instances (i.e. instances of classes implementing the System.IDisposable interface).

The real-time information presented gives a good overview of the activity and status of the GC heap, but by collecting snapshots of the heap, very detailed information can be presented. A heap snapshot can optionally include the instance data of each instance on the heap, allowing the presentation of field values of instances. It is also possible to compare two snapshots, which is a very convenient and efficient way of detecting memory leaks in a program. The memory profiler also helps locating sections of the program which perform excessive allocations. "

Sounds interesting.

I'm going to want to give this App a go. Have an app that after weeks of running appears to have a small leak. The code has been looked at a number of times and nothing stands out (everything seems to be being closed, disposed, etc, etc).

Maybe this utility will help us focus on a specifc area to review.

Since it's free to try for 14 days, seems silly not to try it...

(via Rays of Thoughts - Find Memory Leaks and Optimize Memory Usage in Programs Written in Any .NET Language

No comments: