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

Debugging stalls on wasm pause evaluator when runtime is paused #233428

Open
connor4312 opened this issue Nov 8, 2024 · 0 comments
Open

Debugging stalls on wasm pause evaluator when runtime is paused #233428

connor4312 opened this issue Nov 8, 2024 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release

Comments

@connor4312
Copy link
Member

connor4312 commented Nov 8, 2024

Following a case of #232651

  1. Make a Vite react app
  2. Set a breakpoint and try to debug
  3. Sometimes you get into a stalled state

This seems to be a potential bug(?) or at least a niche behavior in Chromium that prevents (i.e. blocks on) any kind of script execution at instrumentation pauses. Even sending normal REPL-type evaluations at instrumentation pauses don't work. This causes an issue because in some code paths the WebAssembly interception script is first applied during an instrumentation pause. Unfortunately I don't see much of a way around this aside from having a timeout and/or just not awaiting the break application when at an instrumentation pause.

Workaround: Users can work around this either by using js-debug nightly (where this fix is available), or setting "pauseForSourceMap": false in their launch.json. But I think we should take a candidate fix here because it breaks the "hello world" of some common scenarios.

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release labels Nov 8, 2024
@connor4312 connor4312 added this to the October 2024 Recovery 3 milestone Nov 8, 2024
@connor4312 connor4312 self-assigned this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release
Projects
None yet
Development

No branches or pull requests

1 participant