Error processing "breakpointLocations" about vscode-chrome-debug-core

[benwinding]

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

[millsp]

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

[roblourens]

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?

[riteshgrandhi]

vscode-node-debug2.txt

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

Edit: Correct file

[millsp]

thanks @roblourens

[chavychaze]

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

[DrakenKor]

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

[leodinas-hao]

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.

[poorren]

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

[roblourens]

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