Closed ericmattingly closed 3 years ago
Talked with @ericmattingly offline. I have submitted the problem upstream team for further analysis. Tag @sywhang.
@ericmattingly Thanks for the report. @sywhang found the issue. It is a bug in our backend service. I will issue an fix there. It will take a couple of weeks before it hits the service. At the same time, please ignore the BROKEN for now. Other than showing the broken node, the call tree should still be trustworthy.
Thanks @ericmattingly for reporting the issue & @sywhang for point out where the issue is.
I'll keep this issue open until our backend service is deployed with the fix.
The deployment for this fix has started. It will take about 1 week for it to reach global if everything goes smoothly.
The change has been deployed. Feel free to open new issues if there's anything else.
I have the 2.2.0-beta6 profiler enabled on a .NET Core 3.1 service running in a Linux Alpine container in AKS.
Every profile tree seems to have broken stacks. What's my next steps for troubleshooting?