You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
Following a case of #232651
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.The text was updated successfully, but these errors were encountered: