I want to determine the source of the huge amount of memory in my application. My application has a lot of virtual memory (VM column in task manager or private bytes in VMMap)
My application is a .net service, but it uses C # wrappers around C ++ objects.
I tried profiling Red Gate Ants Memory, but it only takes into account managed objects and does not take into account the memory allocated by the unmanaged C ++ new operator (which just calls Virtual Alloc).
Another problem with the managed memory profiler is that it does not allow you to track the call schedule - see the figure below.
