Error processing "breakpointLocations"

I'm getting the following error when setting and unsetting breakpoints on sourcemapped code, specifically when setting breakpoints on lines that would result in extra generated lines.

Error processing "breakpointLocations": TypeError: Cannot read property 'line' of undefined
    at breakpoints.forEach (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/transformers/baseSourceMapTransformer.js:156:55)
    at Array.forEach (<anonymous>)
    at EagerSourceMapTransformer.setBreakpointsResponse (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/transformers/baseSourceMapTransformer.js:147:29)
    at NodeBreakpoints.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/breakpoints.js:309:69)
    at Generator.next (<anonymous>)
    at fulfilled (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/breakpoints.js:7:58)

My use case is sourcemapped coffeescript, for example:

foo = {}
foo.bar = 1 # breakpoint here is fine
if foo.too?.length > 0 # breakpoint here results in error
  console.log('something') # breakpoint here is fine

It looks like the error is emitted from this function, but I don't have a dev environment set up to the point that I can pursue this further:

vscode-chrome-debug-core/src/transformers/baseSourceMapTransformer.ts

Line 188 in 31d1923

breakpoints.forEach((bp, i) => {

Can you try running with "trace": true in your launch config, then upload the log file from the path it prints at the top of the debug console?

vscode-node-debug2.txt

I ran into the same issue, here is the log file

Edit: Correct file

Same here. I've been trying to track this down for a few weeks. It was previously failing silently (breakpoints not always breaking), so I don't think this was introduced in this last release.

(For info, I am using ts-node)

debugadapter.txt

thanks @roblourens

I got a similar error in VS Code, and I have no idea where it comes from, but the application works fine anyway

I have the same issue, but debugger is running fine anyway.

I just removed all breakpoints and the error disappeared...

I have the same issue in vscode & as per @benwinding mentioned, removing the breakpoints fixed the issue. There is no issue with the codes. I believe it's some bug with the debugger.

I find this bug when I configured babel for debug. Before that, the debugger seems fine.

Should be fixed in the latest Insiders build, please let me know if not.