Those pesky memory-leak issues.....

 

Dot Net 2.0 runtime

CLR Profiler for the .NET Framework 2.0
How To: Use CLR Profiler

 

launch profiler
[turn off Profiling active (if app has some setup that doesn’t need profiling)]
Start Application
[turn on Profiling Active]
run app
close app
Select Kill application
Show Heap Now

 

See also

 

Tags

debugging