While in a profiling session, after taking a couple memory snapshots, I see a menu item under View called "Call stack functions" but it is grayed out and disabled. I saw the documentation topic called "Call stacks view" but it doesn't explain how to actually get there. Viewing call stacks is the most important feature to me, to be able to figure out the code path which is actually causing the leak. I was disappointed with the tool that it is so hard to figure out.
I also am using a different .NET profiler product which shows the call stacks of allocations (sortable by # and total amount of allocations) and I was able to find it without even looking at the documentation, so I know this can be done. Unfortunately that other tool doesn't handle attaching to a service process which is what I need now, which the .NET Memory Profiler seems to handle well.
To get allocation call stack information you need to start the profiled process from the profiler, e.g. by using the Profile application command.
SciTech Software AB
Users browsing this forum: Google [Bot] and 25 guests