debugger stopped at bootstrap.js

[haolly]

• VSCode Version: 1.16.0
• OS Version: win10

Steps to Reproduce:

1. Follow instruction https://code.visualstudio.com/docs/extensions/yocode
2. F5

debugger stopped at bootstrap.js

Reproduces without extensions: Yes

[isidorn]

Uncheck the All Exceptions checkbox in the breakpoints pane in debug.
If that still does not work please provide more details. Like a video or picture would help

[haolly]

@isidorn This only happen when I press F5

[yuyat]

+1

[isidorn]

The stop on excpetion is coming from the node2 debug adapter, forwaring to @roblourens
fyi @weinand

[roblourens]

Maybe it took too long to launch, and thought it needed to stop on entry.

Does it happen 100% of the time?

[bhughes339]

@roblourens This is happening for me as well, and it doesn't happen 100% of the time. I'd say probably 90% of the time when I debug (a vscode extension in my case) the bootstrap.js breakpoint fires. It seems this is the relevant code from module.js in node_internals, retrieved from the call stack:

if (process._debugWaitConnect && process._eval == null) {
  if (!resolvedArgv) {
    // we enter the repl if we're not given a filename argument.
    if (process.argv[1]) {
      resolvedArgv = Module._resolveFilename(process.argv[1], null);
    } else {
      resolvedArgv = 'repl';
    }
  }
  // Set breakpoint on module start
  if (filename === resolvedArgv) {
    delete process._debugWaitConnect;
    const Debug = vm.runInDebugContext('Debug');
    Debug.setBreakPoint(compiledWrapper, 0, 0);
  }
}

[roblourens]

Yeah, we expect it to break there, then we set breakpoints and continue. But if it takes a really long time to start up, then we stop waiting for that break event.

Can you set "trace": true in your launch config? It will create a log file and write the path in the debug console. Then upload that log file here. Thanks!

[bhughes339]

vscode-node-debug2.txt

Looks like line 84 is when it breaks on bootstrap.js. I halted the debug after reaching the breakpoint.

[roblourens]

Thanks for the log! I think I found it although I couldn't repro... please try it in the Insiders build tomorrow.

[bhughes339]

Thanks @roblourens. I tried today's Insiders build (1.17.0-1505884649) and I'm still having the issue. Here's my tracelog:

vscode-node-debug2.txt

For the record, I debugged the exact same extension on a Win10 machine with identical settings, and I was unable to reproduce the issue.

[roblourens]

One more update, try again with the next build :)

[bhughes339]

Looks like this issue is resolved in today's Insiders build, at least for me. Thanks again @roblourens!