Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Why is it that when I'm running my application through the profiler a large amout of memory is getting used? This does not occur when we donot use the profiler.
- Posts: 1029
- Joined: Wed Mar 02, 2005 7:53 pm
The profiler itself uses substantial amounts of memory to keep track of all allocated instances and call stacks. Additionally, the amount of unidentified memory increases when running under the profiler (especially when native memory profiling is not active). We have tried to identify why the memory usage differs so much when running under the profiler. We have not been able to find an answer, but we believe that the runtime has different memory characteristics when running under the profiler.
In the next version the native memory profiling is replaced with "low impact profiling" (it's almost the same thing, except that "low impact profiling" actually performs a GC when collecting a snapshot). This will lower the memory overhead when profiling, and you will get more accurate native memory information, however some features will be disabled (e.g call stacks will not be presented).
SciTech Software AB
Users browsing this forum: Google [Bot] and 11 guests