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

Memory profiling for .NET developers

Moderators: Luke Jefferson, Bart Read, StephenC, AndrewH, melvyn.harbour, james.billings, Laura Morley, dene.boulton

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

Postby smcekan » Tue Aug 14, 2012 4:10 pm

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?
Posts: 1
Joined: Tue Aug 14, 2012 4:07 pm

Postby dom.smith » Wed Aug 29, 2012 4:02 pm

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/c ... p_counters
Dominic Smith,
Project Manager,
Red Gate Software.
Posts: 94
Joined: Thu Jun 03, 2010 5:54 pm
Location: Cambridge, UK

Postby Chris.Allen » Tue Sep 25, 2012 1:22 pm

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 :)
Posts: 594
Joined: Thu Mar 12, 2009 4:17 pm

Return to ANTS Memory Profiler 7

Who is online

Users browsing this forum: No registered users and 0 guests