This Question is Answered

2 "helpful" answers available (2 pts)
2 Replies Last post: Apr 4, 2012 8:07 PM by Mikhail Pilin  
Joe Strommen Newbie 2 posts since
Apr 4, 2012
Currently Being Moderated

Apr 4, 2012 6:09 PM

"Unsafe stack walking" in profiler results


    When I profile my application with dotTrace 5.0, a large percentage of the running time shows up as "[Unsafe stack walking]".  I've been unable to find any documentation about this.  What exactly does this mean?



Joe Strommen

Mikhail Pilin JetBrains 538 posts since
May 23, 2005
Currently Being Moderated
Apr 5, 2012 12:27 AM in response to: Joe Strommen
Re: "Unsafe stack walking" in profiler results

Hi Joe,


The sampling profiler generates stack traces for managed threads by timer. So, there are some reasons when profiler can not get managed stack trace:

- only native code on stack

- unsafe time to walk on stack (for example: can't get thread context, some restriction in inside CLR, ...)

We shows that time in special nodes: [native or optimized code] & [unsafe stack walk] as you can see.


We also have some improvements in our x86/x64 stack walker. Now it's under stress testing. So, I belive that dotTrace 5.0.1 will contain it. New stack walker should decrease time for [...] nodes.


Mikhail Pilin
Senior Software Engineer
JetBrains GmbH
"Develop with pleasure!"

More Like This

  • Retrieving data ...