We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AFAIK the allocation profiler added in 1.8 doesn't have a native way to view the output, akin to Profile.print().
Profile.print()
It seems reasonable to expect Profile to be able to make a basic report, and not fully depend on external packages (PProf / the vscode extension)
Profile
The text was updated successfully, but these errors were encountered:
(For those who land on this issue but not #45268...) @vtjnash shared some code for a Profile.Allocs.print (#45268 (comment)): https://gist.github.com/vtjnash/c6aa4db9dafccb0fd28a65f87d6b1adb
Profile.Allocs.print
I've been trying it out and found it pretty helpful!
What would be needed to get that functionality merged in?
Sorry, something went wrong.
Probably someone writing a couple basic tests and making a PR ;)
No branches or pull requests
AFAIK the allocation profiler added in 1.8 doesn't have a native way to view the output, akin to
Profile.print()
.It seems reasonable to expect
Profile
to be able to make a basic report, and not fully depend on external packages (PProf / the vscode extension)The text was updated successfully, but these errors were encountered: