Open Bug 1978668 Opened 3 months ago Updated 3 months ago

Can we get more informative stacks out of async function resumption for Samply

Categories

(Core :: JavaScript Engine, enhancement, P3)

Product:
Core
Component:
JavaScript Engine
Type:
enhancement

Tracking

()

People

(Reporter: mgaudet, Unassigned)

References

(Blocks 1 open bug)

Details

Jeff points out that in this profile we don't have a great stack for the call to DecodeBlob. You can figure out through spelunking that it's coming from _readData, however since this is an async function and we're looking after an await, the stack samply sees here is all the async-resumption machinery with no hint of the original call frame.

I wonder if we could make it so that stack walking code is able to determine that the child of AsyncFunctionNext is a specific JSFunction.

You need to log in before you can comment on or make changes to this bug.