ANTS Memory Profiler - 6.0

ANTS Memory Profiler

Learning ANTS Memory Profiler - 6.0

Understanding unmanaged memory leaks

Managed .NET code may interoperate with unmanaged code when some COM objects or C-style DLLs are invoked.

Leaks caused by unmanaged objects are more complex to identify, because ANTS Memory Profiler cannot provide detailed information about unmanaged usage. You can compare the different performance counters provided by ANTS Memory Profiler, however, to give some ideas about where to look for these leaks.

The main indication of an unmanaged memory leak is when the number of private bytes (the amount of real and paged memory requested by the program) increases while the number of bytes in the .NET heap does not grow as quickly. You may be able to find the source of the problem by looking for .NET objects whose instance count is increasing, or by looking for objects on the finalizer queue that have not been disposed.

Further information

See also

Finding and fixing a memory leak

Was this article helpful?

Search support
Forums

ANTS Memory Profiler

all products