Native stack traces without resolved functions in iisexpress timeline

How to identify the code causing Native stack traces without resolved functions?

Which is the correct way to find the code section which is causing the CPU spike specially when dlls are referred via nuget? 


Thank you!

1 comment
Comment actions Permalink


About the "Native stack traces without resolved functions": such stack traces are caused by native parts of a profiled application, dotTrace can't profile native code yet. For IIS or IIS Express, the high amount of native stack traces in a snapshot is an absolutely normal situation because IIS (or IIS Express) is a native application itself. So you need to skip this node and analyze the rest part of the call tree.

And about the second question - please see the following section of our documentation:

Please let me know if you have any additional questions.



Please sign in to leave a comment.