microsoft / microsoft/vscode-js-profile-visualizer
Error when loading heap snapshot
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 158
- Forks
- 30
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 8
Description
Hey there, as far as I can tell, I'm using the tool correctly, although I haven't had a chance to debug locally. Just received this error when attempting to load a .heapsnapshot file generated today.
Error: RuntimeError: unreachable at wasm://wasm/000b0852:wasm-function[127]:0x1f244 at wasm://wasm/000b0852:wasm-function[184]:0x24977 at wasm://wasm/000b0852:wasm-function[183]:0x24882 at wasm://wasm/000b0852:wasm-function[118]:0x1e96e at wasm://wasm/000b0852:wasm-function[71]:0x192f3 at wasm://wasm/000b0852:wasm-function[44]:0x11d17 at z (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.vscode-js-profile-table/out/425.heapsnapshotWorker.js:1:1869) at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.vscode-js-profile-table/out/heapsnapshotWorker.js:1:2855
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the reported .heapsnapshot file and inspect the heapsnapshotWorker.js entry points shown in the stack trace. Determine why loading reaches the WebAssembly unreachable error, then verify that the same heap snapshot loads without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100