search

microsoft / vscode-js-debug

A DAP-compatible JavaScript debugger. Used in VS Code, VS, + more
MIT License
1.67k stars 283 forks source link

'paused on debugger statement' when debugging vscode extension #2105

Closed adrianstephens closed 1 month ago

adrianstephens commented 1 month ago

Describe the bug When I debug a vscode extension with the nightly debugger, it stops two times with 'paused on debugger statement' before it gets to my extension.

To Reproduce Steps to reproduce the behavior:

  1. Create a vscode extension (or use any of the sample ones)
  2. Hit F5
  3. Note the debugger stopping with 'Paused on Debugger Statement'
  4. Hit F5
  5. Note the debugger stopping with 'Paused on Debugger Statement' again
  6. Hit F5
  7. Debugging continues as usual

Log File vscode-debugadapter-4c089f80.json.gz

**VS Code Version:1.94.0

Additional context

This is the stack on the 1st stop:

(Unknown Source:3) Promise.then (Unknown Source:0) WebAssembly. (Unknown Source:3) (/internal/deps/cjs-module-lexer/dist/lexer:1) await (Unknown Source:0) init (/internal/deps/cjs-module-lexer/dist/lexer:1) initCJSParse (/internal/modules/esm/translators:89) commonjsStrategy (/internal/modules/esm/translators:343) callTranslator (/internal/modules/esm/loader:272) moduleProvider (/internal/modules/esm/loader:278) await (Unknown Source:0) ModuleJob (/internal/modules/esm/module_job:67) #createModuleJob (/internal/modules/esm/loader:290) getJobFromResolveResult (/internal/modules/esm/loader:247) getModuleJob (/internal/modules/esm/loader:228) await (Unknown Source:0) (/internal/modules/esm/module_job:87) link (/internal/modules/esm/module_job:86) await (Unknown Source:0) ModuleJob (/internal/modules/esm/module_job:99) this is the 2nd call stack: (Unknown Source:3) Promise.then (Unknown Source:0) WebAssembly. (Unknown Source:3) lazyllhttp (/internal/deps/undici/undici:5560) await (Unknown Source:0) lib/dispatcher/client-h1.js (/internal/deps/undici/undici:5604) __require (/internal/deps/undici/undici:6) lib/dispatcher/client.js (/internal/deps/undici/undici:7289) __require (/internal/deps/undici/undici:6) lib/dispatcher/pool.js (/internal/deps/undici/undici:7750) __require (/internal/deps/undici/undici:6) lib/dispatcher/agent.js (/internal/deps/undici/undici:7833) __require (/internal/deps/undici/undici:6) lib/global.js (/internal/deps/undici/undici:7933) __require (/internal/deps/undici/undici:6) (/internal/deps/undici/undici:13172) compileForInternalLoader (/internal/bootstrap/realm:398) requireBuiltin (/internal/bootstrap/realm:429) fetch (/internal/bootstrap/web/exposed-window-or-worker:69) DH.globalThis.fetch (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158)
connor4312 commented 1 month ago

Should be fixed in tonight's nightly with https://github.com/microsoft/vscode-js-debug/pull/2103

adrianstephens commented 1 month ago

Thank you so much for such a speedy fix!

ronaldmiranda commented 1 month ago

Oh god, is there another way to disable it? It's so annoying.

connor4312 commented 1 month ago

Update your version of js-debug.