Chrome 114 profiler output change result in speedscope not rendering the stack trace anymore about speedscope

[jlfwong]

Ahhh thanks for the heads up. That's a huge bummer -- a fatal problem with building tools on proprietary file formats.

Not sure when I'll have time to look at this, but good to know.

If someone else would like to take a crack at this, https://github.com/jlfwong/speedscope/blob/main/src/import/chrome.ts is the code that deals with current versions of the chrome profile format.

On a chance guess, I'll bet they switched to using the trace event format described here: https://github.com/jlfwong/speedscope/blob/main/src/import/trace-event.ts

If I do start working on this, I'll leave a message here to indicate as such to avoid duplicating work.

[shuhaowu]

Thanks for the quick response. It's a huge disappointment indeed. I use speedscope almost daily just for the merged flamegraph (left heavy) so I can see the hotspot of an application. I guess I can downgrade to 113 but it's a hassle. If I have some time I might look into this, but it's unclear if I'll have time.

Further, what was like a 10MB trace can be now like 400+MB. Just processing this file will be quite time and memory consuming...

[jlfwong]

Okay, I can repro the issue. I'll look into it

[jlfwong]

@shuhaowu Thanks for the report, the fix should be live on https://www.speedscope.app/ now!