-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Heap snapshots aren't viewable in vscode viewer #52680
Comments
@vilterp from your work, do you have any idea why this happens? |
I don't immediately know 😕 Seems like we'd have to find the source of the vscode viewer and look through it til we find what it doesn't like… |
Chased it over to this repo and it looks like they wrote the It does have a |
Great. I think part of the problem may be their extension suppressing the actual error. If we can figure out how to use the rust decoder directly it might just give a better error? |
Indeed, ran their tests on our file and got
Looks like we'd need to match these fields exactly for the rust parser to work as-is: https://github.com/microsoft/vscode-v8-heap-tools/blob/c5b34396392397925ecbb4ecb904a27a2754f2c1/v8-heap-parser/src/decoder.rs#L48-L50 |
Are they easy to drop in and leave empty? I think the vscode viewer has a graph viewer that might be interesting for your other work |
Yes, I think we should be able to drop them in and leave them empty. What does the graph view look like? When I use it in my vscode I only see a table. |
Great. There's a screenshot here https://code.visualstudio.com/updates/v1_85#_visualize-heap-snapshots |
vscode now has a built in heapsnapshot viewer that seems more powerful than the chrome devtools one.
Unfortunately julia-generated heapsnapshot files do not open and report
Error: invalid profile JSON
, whilst they open in devtools.File sizes:
Error: invalid profile JSON
)Asked upstream at microsoft/vscode#199239 (comment) with a file attached.
Both files validate in jsonlint.com
Headers:
julia's
Chrome's
cc. @NHDaly
The text was updated successfully, but these errors were encountered: