Using ANTS profiler increases memory (private bytes)
Bharadwaj
Posts: 2
I have a .NET 1.1 based windows application which is consuming close to 80 MB (Private bytes)..which is very high based on our requirements. I decided to use ANTS profiler to profile the memory and identify heavy duty data structures and memory leaks.
But when I attach the ANTS profiler to my application, the memory consumption of my application (private bytes) actually increases to 110-120 MB. And this is happening everytime I profile my application. The same happens when I use the CLR profiler also.
I am measuring the private bytes on my process through the performance monitor.
I am not sure why this is happening?
But when I attach the ANTS profiler to my application, the memory consumption of my application (private bytes) actually increases to 110-120 MB. And this is happening everytime I profile my application. The same happens when I use the CLR profiler also.
I am measuring the private bytes on my process through the performance monitor.
I am not sure why this is happening?
Comments
When profiling is enabled, the back-end component sits in the memory space of your application. You would gee generic memory counters reflect this. If you want to see what your application is using on its' own, I think you're better off looking at some of the counters in the .NET Memory object, such as the number of bytes in all heaps for an application.