Skip to content

no deopts in visualization, but plenty in --trace-deopt output? #30

@softwareCobbler

Description

@softwareCobbler

doing

~$ node -v
16.13.2
~$ node --trace-deopt --prof app
~$ deoptigate

writes the --trace-deopt output to the console, and the --prof generates the log file that deoptigate builds its visualization from. Chrome pops up and renders out the visualization, so far so good!

But, in the visualization, there are no deoptimizations listed, whereas the --trace-deopt output has plenty of (~100) deoptimizing [address] <JSFunction> ....

I'm not sure if I'm using the tool correctly, but I was expecting deoptigate to render a visualization of the same deoptimizations that --trace-deopt detects (which is what led me here, I don't know enough about v8 internals to use the raw --trace-deopt output for any perf gains, figured a visualization would point to "this property access triggers deopt" or etc.).

thanks for your time!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions