Vscode-js-debug: Debugger should reevaluate breakpoints when new sources with the same absolutePath come in

[evgenyFinkin]

I have a proxy and some process running and the debugger doesn't stop

[viceice]

Here too, workaround s to add a debugger statement to initial break. After it you can add normal breakpoint, which are hit as usual.

[viceice]

Reproducable here: https://github.com/renovatebot/renovate

Works here: https://github.com/renovatebot/ruby-semver

The difference is renovate is using jest-circus instead of jest-jasmine as testRunner and using babel-jest instead of ts-jest for typescript transform.

[connor4312]

@evgenyFinkin please collect a trace log using these instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to [email protected]

@viceice it sounds like you're hitting https://github.com/microsoft/vscode/issues/102152. This was fixed in the latest [nightly build](https://github.com/microsoft/vscode-js-debug#nightly-extension.

[Megabyteceer]

Same issue. I noticed that for scripts loaded asynchonically breakpoints does not work until you remove and set breakpoint again. I think resend brekpoints to browser after new script loaded will fix all such a bugs.

[YuryKuvetski]

Same picture as @Megabyteceer described. Realy slows down development 😞

[connor4312]

@Megabyteceer @YuryKuvetski please collect a trace log using the instructions posted above.

[Megabyteceer]

Logs:
vscode-debugadapter-0.json.gz

What i did. Set breakpoint first time, its stopped fine. Page have reloaded dynamically few js scripts. Break point stop working because it was inside one of reloaded scripts. I remove and set this breakpoint and after that breakpoints works fine again.

[connor4312]

Okay, thanks. It looks like the issue in this case is because the URL changed between reloads -- the breakpoint was set in ?v=1, but after reload the script was ?v=2, and we don't re-evaluate a breakpoint when a new source comes in (only a sourcemap, at the moment). I will look at fixing this, but this is a somewhat esoteric build/reload setup, so it may be a little while before I have an opportunity to fix this.

The original author hasn't yet provided more info, so until that happens I will make this issue about the problem you're facing 🙂

[DJ4ddi]

What's the status on this?

I'm having the same issue, which is that scripts with deferred loading (basically everything since I'm working on an Electron app) always lose their breakpoint bindings. As described above, simply disabling and enabling each breakpoint restores the binding, but this is not satisfactory because it prevents me from debugging initialization logic.

Using the old debugger (by disabling the preview), everything works as expected.

I'm on VSCode version 1.51.1 and Debugger for Chrome version 4.12.11

[connor4312]

This is fixed. If you are still experiencing issues, please open a new issue and include the info from the template. Thanks.

[Megabyteceer]

For me breakpoints still stop working, when i reload same script with ?v=2 parameter.