title: async profiler displays wrong stacktraces
body: <p>I am trying to use <a href="https://github.com/jvm-profiling-tools/async-profiler" rel="nofollow noreferrer">async profiler</a> v.1.8.1 for profiling my application.</p>
  <p>JVM is openjdk version &quot;15-ea&quot; 2020-09-15, but same happened with openjdk 14.0.1 as well.</p>
  <p>async profiler is run with flags: -d 60 -t -i 10000 -o svg</p>
  <p>It shows extremely strange results. <a href="https://i.stack.imgur.com/1uoOL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1uoOL.png" alt="enter image description here" /></a> We can see that hardware thread spends most of the time not in java.lang.Thread::run, but in some weird place. How can it be explained? I see a possible explanation that async profiler fails to properly traverse stack traces and puts part of these stack traces in a wrong place. Is there another explanation? How can it be fixed?</p>