microsoft / vscode

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

Process Explorer does not show process vsdbg-ui #141245

Open yecril71pl opened 2 years ago

yecril71pl commented 2 years ago

Issue Type: Bug

When a program is being debugged, it can be terminated from the Process Explorer. However, sometimes this is impossible because the Process Explorer shows neither the program vsdbg-ui nor the dotnet program being debugged. Sometimes this branch appears after some time, sometimes it does not.

Workaround: use System Monitor instead. This tool sometimes erroneously shows the debugged process to have the same command line as the debugger itself, in which case the process is unexpectedly named Protocol (rather than dotnet).

VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:39:46.686Z) OS version: Linux x64 5.16.1-1-default Restricted Mode: No

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 x 2394)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|1, 1, 1| |Memory (System)|5.66GB (0.21GB free)| |Process Argv|--unity-launch --crash-reporter-id 2a03cb52-9f4b-48bf-93d3-5c0537d534ee| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|/usr/share/xsessions/plasma5| |XDG_CURRENT_DESKTOP|KDE| |XDG_SESSION_DESKTOP|KDE| |XDG_SESSION_TYPE|x11|
Extensions (28) Extension|Author (truncated)|Version ---|---|--- doxdocgen|csc|1.3.2 vscode-resx-editor|Dom|0.0.5 gitlens|eam|11.7.0 vscode-pull-request-github|Git|0.34.3 githd|hui|2.2.4 Ionide-fsharp|Ion|5.10.2 better-cpp-syntax|jef|1.15.10 vscode-language-pack-pl|MS-|1.63.3 csharp|ms-|1.24.0 dotnet-interactive-vscode|ms-|1.0.2606010 vscode-dotnet-pack|ms-|1.0.5 python|ms-|2021.12.1559732655 vscode-pylance|ms-|2022.1.3 jupyter|ms-|2021.11.1001550889 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.4 remote-containers|ms-|0.209.6 remote-ssh|ms-|0.70.0 remote-ssh-edit|ms-|0.70.0 remote-wsl|ms-|0.63.13 cmake-tools|ms-|1.9.2 cpptools|ms-|1.7.1 cpptools-extension-pack|ms-|1.1.0 powershell|ms-|2021.12.0 vscode-markdown-notebook|ms-|0.0.26 vsliveshare|ms-|1.0.5273 vsliveshare-audio|ms-|0.1.91 cmake|twx|0.0.17 (1 theme extensions excluded)
A/B Experiments ``` vsliv368:30146709 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyl392:30425749 pythontb:30283811 pythonvspyt551cf:30345471 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 pythondataviewer:30285071 vscod805:30301674 pythonvspyt200:30340761 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 vsc1dst:30424896 pythonvs932:30410667 vscop804cf:30404767 vscop940:30404999 vsrem710:30416614 vsbas813:30426126 vsic-wlc-tsjs:30426436 ```
Tyriar commented 2 years ago

The process explorer only looks at the process tree under VS Code's main process, are these vsdbg-ui or dotnet processes detached from that tree?

yecril71pl commented 2 years ago

The processes being run are child processes of the environment unless of course they voluntarily daemonise. My processes did not.