v4.12.9 - Debugger for Chrome extension with angular9 lunching the page very slowly

[AvshT]

VS Code Version: 1.46.1+ Angular 9.1.12

If you go to the previous version, it working fine.

My assume is that you've remove the type:"chrome" option from launch.json And the use of type: "pwa-chrome" is not working as expected.

Any code recompile cause the slowness reload.

Please fix it ASAP.

[roblourens]

cc @connor4312

[connor4312]

This may be the same as https://github.com/microsoft/vscode-js-debug/issues/598

Please try our nightly build to see if that fixes it for you!

[waldnercharles]

I've run into this issue as well; downgrading to 4.12.8 works if you don't want to upgrade to nightly.

[chucknelson]

VS Code Version: 1.47.3 Angular 8.0.0

Experiencing the same issue with an Angular 8 project, in addition to breakpoints no longer working (although in the logs, it looks like sourcemaps are resolving correctly).

Also able to restore working behavior by rolling back to version 4.12.8 of the extension.

[connor4312]

@chucknelson this should be fixed in https://github.com/microsoft/vscode-js-debug/issues/598

Please try our nightly build to see if that fixes it for you!

[chucknelson]

Thanks @connor4312 - saw the note above but I don't think I was realizing the connection between vscode-js-debug and this extension! I'll try this out and update here.

I guess the latest version of the Chrome Debugger (4.12.9) is defaulting to use this new debugging backend...differently than 4.12.8? I'll have to look again so I can get this straight in my head...

[chucknelson]

@connor4312 - Alright, so after some more trial and error:

• As you've stated, the slow performance of Angular apps using js-debug (via pwa-chrome launch config type) is fixed in the nightly build version - thanks!

• The breakpoints not working seems to be differences in how js-debug and the "legacy" debugger-for-chrome work. For my VS Code Remote SSH development, I needed to specify my webRoot as where my main app was in my Angular project, and the following had to be added to my custom sourcemaps to get breakpoints working:

  // For debugging remotely with VS Code Remote (e.g., connecting to a VirtualBox VM)
  "webpack:////*": "/__vscode-remote-uri__/*"

  Now if I change my webRoot to just / and don't override sourcemaps, things work. Now I'm wondering if the project will still work if I use a normal local setup, like native Windows dev. I'll try that out later...

• Finally, something definitely changed in how the debug-for-chrome extension treats its default debugging "engine" - 4.12.8 seems to use the legacy debugger, and 4.12.9 seems to use js-debug, even though the CHANGELOG says it defaulted to js-debug via debug.javascript.usePreview back in 4.12.7. So 4.12.8 seems to be the outlier/bug, but was just confusing at first :sweat_smile:

@roblourens , @connor4312 - Anyway, for this particular issue, I would vote to close it since it's caused by js-debug, and has already been fixed in nightly.