I'm trying to determine who is allocating (and failing to free) many large blocks of unmanaged memory in our application. The "Unmanaged memory breakdown by module" pane shows that all of this memory is allocated by MSVCR120 (Microsoft's C Runtime Library). Is it possible to look further up the call stack?
Comments
1 comment
-
Hi @LWatt!
It's not possible to view the call stack from the memory profiler, I'm sorry to say. When you take a look at the class list though, you can see how much unmanaged memory each managed class references via the "Unmanaged size" column and that might help determine where it's coming from - you can check which managed classes are holding on to the most unmanaged memory. (Note though: you unfortunately can't see what modules that unmanaged memory belongs to.)
Add comment
Please sign in to leave a comment.