Memory leaks, the free way

In case you want to check the Memory leaks of your applications I recommend the following strategies:

1- Define a single scenario, AKA that is repeatable and does not depends on others or influence on them

2- Isolate the scenario if possible from application reactions, for example if the scenario calls other components

3- Check it with Task Manager following the interesting counters, like Virtual Memory, Allocated Memory, etc

4- If you find leaks, try use the CLRProfiler, for the moment use the Framework 2.0

It’s free, the interface is +/-, the operability is –, and the results once you understand the GC and the Heap are stunning

You can use PerfMon to follow repeatable scenarios in the background (Run it from CLI)

If you have money the best Memory profiler is called…Memory Profiler, is much clear and friendly and sharp, they have a shareware version

Inside VS there are other tools under Analyse Menu toolbar, they are more related to CPU, and can be also operable from CLI