Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

chucknelsoncommented, Aug 1, 2020

@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 😅

@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.

0reactions

chucknelsoncommented, Jul 30, 2020

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…

Top Results From Across the Web

Angular 2 Application reacting very slowly only while Chrome ...

Maddeningly, when I run the DevTools' Timeline "Record" to try to gain visibility into the issue, the issue disappears and the page reacts...

DevTools Overview - Angular

Angular DevTools is a browser extension that provides debugging and profiling capabilities for Angular applications. Angular DevTools supports Angular v12 ...

Case Study: Better Angular Debugging with DevTools

Using Angular as a test pilot, the Chrome DevTools and Angular teams collaborated to offer you a better debugging experience.

Microsoft - Bountysource

Recently I upgraded Chrome Debugger from v4.12.9 to v4.12.10, upgraded VS Code to the latest 1.48.2. When I hit F5 for debugging, it...

This page is not using Angular, or it has a strict extension policy.

On installing the extension in chrome where a tab had already loaded the angular page then selecting the angular tab I was seeing...