Sorry if the question has already been raised, but I did not find it.
In MemProfile 3.5, Tab "Resource details" for VirtualMemory I have a stack like this one:
ntdll!NtAllocateVirtualMemory( HANDLE, PVOID*, ULONG, PULONG, ULONG, ULONG )
[Managed to native transition]
Lcl.Dhpl.Data!<Module>.openFile( basic_string<char,stlp_std::char_traits<char>,stlp_std::allocator<char> >* ) // this is some managed C++ code
[...] // I've cut the rest of managed stack
I'm interested by the Unidentified / skipped frame. Is there something to do in order to get more precision on these frames?
PS: By the way, I find the 3.5 version heap better than the 3.0 which was already a good one: Good job !
[Skipped frame(s)] are added when a stack frame has been skipped by the stack reducer or when excluded by a "Call Stacks" setting. I recommend that you make sure that all managed methods and all native methods are included under the "Call Stacks" settings. To avoid excessive memory usage and slow performance, it is probably a good idea to keep the call stacks reducer enabled, but you can try to increase the number of "Max skippable stack frames" (e.g. from 2,000,000 to 4,000,000).
SciTech Software AB
Users browsing this forum: No registered users and 13 guests