Debugging ANGULAR project in VSCode not working.

[mayank594]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.87.2
• OS Version: Windows 10 Enterprise

Steps to Reproduce:

1. In launch.json created Launch Chrome against localhost as:

{ "version": "0.2.0", "configurations": [ { "type": "chrome", "request": "launch", "name": "Launch Chrome against localhost", "url":"https://anonymous.local:3200/Home/Welcome", "webRoot": "${workspaceFolder}" } ] } The url indicates the login page of the application

2. Putting breakpoints at the required places in the angular code(ts files)

3. Selecting "Launch Chrome against localhost" from and start debugging(f5)

4. Application starts and logged in successfuly, navigate to page where breakpoint will be hitted-> application hangs and nothing happens, neither the breakpoint is reached, after few minutes of wait the break point is reached and when press f10 or f5 this message appears:

I have to then either reopen or close vscode which ends up everything.

This is really frustrating as it hampers my daily development, this was working perfectly fine but from last few updates i am seeing this error.

I have tried uninstalling and re installing vs code, also updated to version 1.87.2 but nothing worked. Please help me out in resolving this on priority.

[vscodenpa]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[connor4312]

Thanks for the issue, unfortunately I'm not able to reproduce it at the moment. Could you share your user settings so I can see if there's something in there I might be missing?

[mayank594]

Hi @connor4312 , as suggested i've updated to the latest version 1.89.1 today and unfortunately the issue still persists.

Whenever I attach a debugger it takes a lot of time to the debugger to hit and if it hits and i try to proceed this message appears after waiting for few minutes and i have to restart vscode .

my launch.json file

This is really frustrating as i have to be dependent on browser dev tools to debug any piece of code. I would really appreciate help from your end.

[connor4312]

Could you share your user settings as well? Thanks!

[mayank594]

Which settings are you referring to?

On Thu, 16 May 2024, 22:26 Connor Peet, @.***> wrote:

Could you share your user settings as well? Thanks!

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/210717#issuecomment-2115763611, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFODZZHTFFJXG6LROREDKDZCTQKZAVCNFSM6AAAAABGOSI76GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVG43DGNRRGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[mayank594]

Could you share your user settings as well? Thanks!

if you can be more specific which user settings you're referring, will share.

[connor4312]

You can open the settings.json though the command Preferences: Open User Settings (JSON)

[mayank594]

settings.json Pls find the file attached.

[mayank594]

@connor4312 any suggestions?

[SPKorhonen]

I have the same problem. When debugging Edge or Chrome the browser crawls to 1/100th of normal speed. If one tries to stop the debug session, VS Code freezes completely. Only using reload from the "window is not responding" -dialog restores functionality.

In my experience using FireFox and "Debugger for Firefox" extension works and I'm currently using it as a work-around.

I also have a colleague who has the same issue. Updating or complete re-install doesn't resolve the issue.

[mayank594]

@SPKorhonen I have seen a lot of people complaining about the same issue however no one got any solution yet. It is really unfortunate that even after opening issue and following up from so months no one from microsoft team seems to be concerned about this. I totally have no hope of this working soon and now mostly rely on chrome dev tools which is a big pain for me, i am planning to shift my all my dev work to some other ide if this continues. As per your suggestion, I will try with debugger for firefox now, Thanks

[SPKorhonen]

Additional datapoints:

• Ms Edge is completely unusable. Slowdown by factor >1000, huge cpu utilization even when page and debugger are idle.
• Brave seems to work just fine based on a few days usage.
• Vivaldi is also viable though noticeably slower than Brave

Thus I'm using Brave as current work-around