-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet-trace: Error in speedscope.app showing with Failed to load format Error: Tried to leave frame #1206
Comments
Looks like this is an error caused by a recent change in Speedscope (jlfwong/speedscope#273) that decided to change behavior and fail hard on some ordering constraints. I'll take a look at our logic for conversion over in Microsoft/PerfView and see if I can figure out what causes the ordering issue. CC @adamsitnik |
Issue in Microsoft/PerfView: microsoft/perfview#1178. Based on the comments here, it looks like we should be able to fix this by picking up the newest TraceEvent version. |
I've provided a fix microsoft/perfview#1212 |
Thanks for fixing it! Is there any schedule for a release that would include this patch? |
Thank you for fixing the problem. However, how do I make use of the fix as I am still getting the error? More details of the error here: https://stackoverflow.com/questions/63020262/why-does-tracing-c-sharp-code-in-linux-fail-when-imported-into-speedscope |
I believe this fix is in the most recent release: https://github.com/dotnet/diagnostics/releases/tag/3.1.137102 |
Yes, it works! 🚀 |
I tried to use dotnet-trace with WSL Ubuntu 18.04 and .NET Core 3.1.300 in my project. I have chosen speedscope output, and I do get trace.speedscope.json file, but it does not open in https://www.speedscope.app/ and browser's Javascript console gives following error:
How to replicate:
dotnet run -c release < /dev/zero > /dev/null
dotnet-trace ps
dotnet-trace collect --process-id PID_HERE --format speedscope
Speedscope tracing works OK in another project of mine
The text was updated successfully, but these errors were encountered: