Skip to content
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

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

Open
softwareCobbler opened this issue Jan 30, 2022 · 1 comment
Open

Comments

@softwareCobbler
Copy link

softwareCobbler commented Jan 30, 2022

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!

@feedthejim
Copy link

FWIW I've had the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants