Kernel Panic/crash Debian (12-bookworm) on VSCode Upgrader Installer running

Type: Bug

I cannot prove it, because it usually (about 1 out of 3 auto-upgrades) succeds on reboot due to kernel-panic (it hangs to a point where I have to hardware shtudown via power-switch off) but if I ssh-remote connect vscode (also happened today on vscode-insider) to my one of my Linux host (Debian 12, with or without X11 installed - well, libs may be installed, but DM (i.e. XDM, GDM3, etc) aren't for it's a headless server) and VSCode detects that I need an upgrade, and I let it auto-upgrade, it goes through the process of downloading the upgrade image and proceeds to install. While it is doing this, it is usually in the state of ssh-remote login so I cannot do anything such as begin looking at my source codes, etc. Then I sometimes notice that my ssh (on another xterm) hung (no response on remote) and when I try pinging it, it's no response. I physically go to that remote host and I notice that it has completely hung and I'd have to manually turn off. Please note that I've lately started to see similar effects on Docker, so it may be due to VSCode shell to be similar to some VM situations that is causing the crash. But I've not done Docker in about 3 weeks, and I'm more in the VSCode domain to do productive stuffs, so I notice it more in VSCode.

VS Code version: Code - Insiders 1.83.0-insider (11bfd76a61a299156a9f3138ecfad70937af3527, 2023-09-21T05:34:38.227Z) OS version: Windows_NT x64 10.0.22621 Modes: Remote OS version: Linux x64 6.1.0-10-amd64

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|15.82GB (4.04GB free)| |Process Argv|--crash-reporter-id 9ab3b74e-8494-4278-8651-04bacdf4c84d| |Screen Reader|no| |VM|0%| |Item|Value| |---|---| |Remote|SSH: shuriken.*****| |OS|Linux x64 6.1.0-10-amd64| |CPUs|AMD Phenom(tm) II X6 1090T Processor (6 x 803)| |Memory (System)|7.51GB (3.56GB free)| |VM|0%|

Extensions (52)

Extension|Author (truncated)|Version ---|---|--- vscode-nginx-conf|ahm|0.3.2 rust-syntax|dus|0.6.1 rust-flash-snippets|lor|3.1.0 vscode-edge-devtools|ms-|2.1.3 jupyter-keymap|ms-|1.1.2 remote-containers|ms-|0.311.0 remote-ssh|ms-|0.106.4 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.81.4 vscode-remote-extensionpack|ms-|0.24.0 remote-explorer|ms-|0.4.1 remote-server|ms-|1.4.3 vim|vsc|1.26.0 SecurityIntelliSense|azs|0.8.0 quicktype-refresh|dog|1.0.2 code-runner|for|0.12.0 msys2|fou|0.10.0 shell-format|fox|7.2.5 copilot|Git|1.114.428 copilot-chat|Git|0.8.2023092101 copilot-labs|Git|0.15.1019 go|gol|0.39.1 cloudcode|goo|2.0.0 Ionide-FAKE|Ion|1.2.3 Ionide-fsharp|Ion|7.12.2 Ionide-Paket|Ion|2.0.0 vscode-docker|ms-|1.26.1 csdevkit|ms-|0.4.10 csharp|ms-|2.1.2 vscode-dotnet-runtime|ms-|1.7.3 vscodeintellicode-csharp|ms-|0.1.26 python|ms-|2023.16.0 vscode-pylance|ms-|2023.9.20 jupyter|ms-|2023.8.1002501831 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.17 vscode-jupyter-cell-tags|ms-|0.1.8 vscode-jupyter-slideshow|ms-|0.1.5 cmake-tools|ms-|1.15.31 cpptools|ms-|1.17.5 cpptools-extension-pack|ms-|1.3.0 hexeditor|ms-|1.9.12 live-server|ms-|0.4.9 json-to-yaml-and-more|pet|0.0.3 rust-analyzer|rus|0.3.1665 crates|ser|0.6.3 cmake|twx|0.0.17 vscode-lldb|vad|1.10.0 intellicode-api-usage-examples|Vis|0.2.8 vscodeintellicode|Vis|1.2.30 vscodeintellicode-completions|Vis|1.0.22 vscodeintellicode-insiders|Vis|1.1.10 (2 theme extensions excluded)

A/B Experiments

``` vsliv695:30137379 vsins829:30139715 vsliv368cf:30146710 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 pythontb:30258533 vsc_aacf:30263846 pythonptprofiler:30281269 vshan820:30294714 vscod805:30301674 bridge0708:30335490 bridge0723:30353136 vsaa593:30376534 pythonvs932:30404738 py29gd2263:30784851 vscaat:30438846 vsclangdf:30492506 c4g48928:30535728 dsvsc012:30540252 pynewext54:30618038 showlangstatbar:30737417 24365598:30687740 pythonfmttext:30716741 fixshowwlkth:30771523 showindicator:30805243 pythongtdpath:30726887 i26e3531:30792625 welcomedialog:30812478 pythonnosmt12:30779711 pythonidxpt:30768918 pythonnoceb:30776497 copilotsettingt:30808721 dsvsc013:30777762 dsvsc014:30777825 diffeditorv2:30786206 pythonlinttype:30823781 pythonmypyww:30841056 pythonmhint1:30815193 dsvsc015:30821418 pythontestfixt:30826906 pythonfb280951:30830809 ```

@roblourens what command should a user run to collect the remote ssh trace logs ? It would good to check remote connection for issues.

Apologies for butting in, but as mentioned in my OP, but I believe they are (at least) already dumped to remote-ssh output window (do not know which one), but I do see it scrolling by with some messages about "downloading", etc. Hence I knew it was during the setup. It's just that (I believe, I may be wrong) when my remote host hangs (panics), I have to close my VSCode, hence I do not pay attention to that remote-ssh logs.

Also, if one is wondering if it is my Linux host that is an issue or not, on my host that has X libraries installed (and on my Windows, if I have my DISPLAY setup correctly), and if I did XForward via ssh to remotely run VSCode-Insider (or VSCode) on my Windows, and such upgrade triggers, majority of the time, it won't upgrade and I'd have to manually download VSCode-Insider .deb package and install ('dpkg -i') it manually. I have though, witnessed once or twice (quite rare) when it has somehow upgraded my VSCode on XForwarded instance and did not kernel-panic, so I'm cannot say whether it's my Debian with X11 that is the problem or it's the actual upgrader.

Finally, as mentioned, when I ssh to one of the handful headless hosts that has Docker running at times, I think I've seen it kernel-panic, but now that I think about it, I was remoting to it via VSCode and testing apps running in Docker containers via VSCode BASH-terminal... There's too many moving parts for me to isolate the problems and in most cases, it's just a reboot of the physical host that panicked and thankfully, all those hosts are LAN...

microsoft / vscode

Kernel Panic/crash Debian (12-bookworm) on VSCode Upgrader Installer running #193698