`SymbolsBackend` init hangs

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, wasm
Domain
devtools

Research direction

Start at the RPC implementation of createSymbolsBackendModulePromise and inspect its WebAssembly.compile call. Compare its behavior with compiling the module in the nose repl; done means the SymbolsBackend initialization resolves and the extension can parse symbols without hanging.

Written by the indexing model from the issue text.

Description

For some reason, when loading the symbol backend wasm, the compilation hangs and never resolves.
The extension isn't able to parse symbols due this hanging. I have looked into this and it seems the call to WebAssembly.compile inside createSymbolsBackendModulePromise (the rpc one) hangs. When compiling the module in the nose repl, it works

Dominant language
TypeScript
Stars
21
Forks
6
Avg merge
8h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-dwarf-debugging

All issues in microsoft/vscode-dwarf-debugging

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.