search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.44k stars 29.35k forks source link

VS Code Debugger is not working #177270

Closed vicky469 closed 1 year ago

vicky469 commented 1 year ago

Type: Bug

Steps to reproduce:

  1. ng serve to start the angular app
  2. run and debug
  3. see a blank page with the spinning icon keep loading

Now: When I debug Angular app in vscode, the debugging chrome instance will be open but the page is blank. If I go to some detailed page, and click back arrow, it will show a few icons for the page for one second then went disappear. This happened since last Friday, previously was good. Looks like only I have this issue, didn't hear other other team members complain about it. I have tried Microsoft Edge too, same issue.

Expected result: Debug needs to be fixed. If the browser is not attached in vs code debugger, I can view content and debug in browser. But I would love to keep debugging in vs code.

Things I tried:

  1. Debugger attach to Edge
  2. Delete all chrome extensions (I don't think this is the issue)
  3. Reopen, reinstall, restart

VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z) OS version: Windows_NT x64 10.0.19044 Modes: Sandboxed: No

System Info |Item|Value| |---|---| |CPUs|11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (16 x 2496)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|undefined| |Memory (System)|31.67GB (17.06GB free)| |Process Argv|--crash-reporter-id 1abdd797-7727-4aa6-aed7-df3f639a7879| |Screen Reader|no| |VM|0%|
Extensions (29) Extension|Author (truncated)|Version ---|---|--- csharp-to-typescript|adr|1.12.1 ng-template|Ang|15.2.0 gitstash|art|5.1.0 path-intellisense|chr|2.8.4 vscode-eslint|dba|2.4.0 githistory|don|0.6.20 gitlens|eam|13.3.2 EditorConfig|Edi|0.16.4 vscode-typescript-exportallmodules|eli|2.6.0 prettier-vscode|esb|9.10.4 json2ts|Gre|0.0.6 angular-essentials|joh|13.0.0 Angular2|joh|13.0.0 vscode-peacock|joh|4.2.2 ts-debug|kak|0.0.6 ts-extension-pack|loi|0.3.0 ts-error-translator|mat|0.8.0 git-graph|mhu|1.30.0 vscode-edge-devtools|ms-|2.1.1 amend-commit-message|Osi|1.0.0 material-icon-theme|PKi|4.24.0 tsimporter|pmn|2.0.1 typescript-hero|rbb|3.0.0 LiveServer|rit|5.7.9 code-spell-checker|str|2.20.0 move-ts|str|1.12.0 tabnine-vscode|Tab|3.6.43 tcv-typescript-constructor-generator|toa|0.2.0 vscode-todo-highlight|way|1.0.5
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vstes627cf:30244335 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242:30382549 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscorecescf:30445987 pythondataviewer:30285071 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593:30376534 pythonvs932:30410667 cppdebug:30492333 vsclangdf:30486550 c4g48928:30535728 dsvsc012cf:30540253 pynewvextcfv2:30681851 azure-dev_surveyone:30548225 vscccc:30610679 pyindex848:30662994 nodejswelcome1cf:30587006 282f8724:30602487 pyind779:30671433 f6dab269:30613381 pythonsymbol12:30671437 a9j8j154:30646983 showlangstatbar:30672706 vscodedisable:30660115 funwalk2:30682974 pythonms35:30686772 ```
vscodenpa commented 1 year ago

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

Happy Coding!

cyberbiont commented 1 year ago

I just wanted to open this issue myself. I'm having the same problem, and seems like it is connected with the latest Chromium update. The problem is evident in all Chromium-based browsers (Chrome and Edge debuggers, as well), but I am still able to use Firefox debugger.

BTW, if I do not any breakpoints set, the page loads normally; once I set the breakpoint and try to reload the page - blank screen.

Barobi commented 1 year ago

I and my team are having the same problem.

Without breakpoints it's still working and I can also add breakpoints after the debugging session was started.

So it seems, there is just a problem with breakpoints set initially.

(As a workaround, breakpoints can be set in Chrome Dev Tools and they will work with the VS Code Debugger)

yarongot commented 1 year ago

It might be fixed with Version 1.76.2 that was updated today.

On Thu, Mar 16, 2023 at 11:24 AM Barobi @.***> wrote:

I and my team are having the same problem.

Without breakpoints it's still working and I can also add breakpoints after the debugging session was started.

So it seems, there is just a problem with breakpoints set initially.

(As a workaround, breakpoints can be set in Chrome Dev Tools and they will work with the VS Code Debugger)

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

Barobi commented 1 year ago

It might be fixed with Version 1.76.2 that was updated today. … On Thu, Mar 16, 2023 at 11:24 AM Barobi @.> wrote: I and my team are having the same problem. Without breakpoints it's still working and I can also add breakpoints after the debugging session was started. So it seems, there is just a problem with breakpoints set initially. (As a workaround, breakpoints can be set in Chrome Dev Tools and they will work with the VS Code Debugger) — Reply to this email directly, view it on GitHub <#177270 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHCCOENQC4RKX2AG6RL6E7LW4LL3ZANCNFSM6AAAAAAV4EVH4U . You are receiving this because you are subscribed to this thread.Message ID: @.>

I'm already on 1.76.2

cyberbiont commented 1 year ago

Without breakpoints it's still working and I can also add breakpoints after the debugging session was started.

So it seems, there is just a problem with breakpoints set initially.

Not for me. if I start without breakpoints, it still breaks, once I set one.

cyberbiont commented 1 year ago

Ok, seems like updating to 1.76.2 indeed fixed it for me.

CorwinDickey commented 1 year ago

My team is also reporting issues. I am able to start a debug session without breakpoints, and so far it appears to work even when a break-point is added later.

After updating to 1.76.2 I was still unable to start a debug session with breakpoints, another update as indicated by the VS Code settings appears to have fixed the issue. I can currently start a debug session with breakpoints already set.

MNorgren commented 1 year ago

My team is also reporting issues. I am able to start a debug session without breakpoints, and so far it appears to work even when a break-point is added later.

After updating to 1.76.2 I was still unable to start a debug session with breakpoints, another update as indicated by the VS Code settings appears to have fixed the issue. I can currently start a debug session with breakpoints already set.

Where do I find this "other update"? I am also on 1.76.2 but am still experiencing this issue.

CorwinDickey commented 1 year ago

My team is also reporting issues. I am able to start a debug session without breakpoints, and so far it appears to work even when a break-point is added later. After updating to 1.76.2 I was still unable to start a debug session with breakpoints, another update as indicated by the VS Code settings appears to have fixed the issue. I can currently start a debug session with breakpoints already set.

Where do I find this "other update"? I am also on 1.76.2 but am still experiencing this issue.

I ran check updates again and it found an update it needed me to restart the app for. After the restart it was working again.

MNorgren commented 1 year ago

It might be fixed with Version 1.76.2 that was updated today. … On Thu, Mar 16, 2023 at 11:24 AM Barobi @.**> wrote: I and my team are having the same problem. Without breakpoints it's still working and I can also add breakpoints after the debugging session was started. So it seems, there is just a problem with breakpoints set initially. (As a workaround, breakpoints can be set in Chrome Dev Tools and they will work with the VS Code Debugger) — Reply to this email directly, view it on GitHub <#177270 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHCCOENQC4RKX2AG6RL6E7LW4LL3ZANCNFSM6AAAAAAV4EVH4U . You are receiving this because you are subscribed to this thread.Message ID: @.**>

I'm already on 1.76.2

Did you figure this out? I am still running into it and I am on 1.76.2. I've restarted VS Code, my computer, etc and have had no luck.

connor4312 commented 1 year ago

https://github.com/microsoft/vscode-js-debug/issues/1604