Why you shouldn't use task manager to determine memory leaks

[smcekan]

Was always told that using task manager was a bad idea for determining if you app had a memory leak. Partly due to the private bytes including allocated & unused bytes.

Is this the case?

[dom.smith]

Task Manager displays only the 'Private working set' memory counter, which is only accurate immediately after a garbage collection. That's probably why you were told this.

For a comparison of the different memory counters available, please see the 'Comparing Memory Counters' section of this page: http://www.red-gate.com/supportcenter/content/ANTS_Memory_Profiler/help/7.4/amp_set_up_counters
_________________
Dominic Smith,
ANTS Performance Profiler Project Manager,
.NET Division, Red Gate Software.

[Chris.Allen]

For what it's worth, IMHO ; there is nothing whatsoever wrong with task manager for detecting leaks.

It just won't tell you *why* there's a leak- that's where ANTS Memory Profiler comes in