Issue Type: Bug
I often have to restart vscode when things get stuck (not the issue).
I am encountering an issue where after I close and reopen vscode (without waiting a bit), vscode starts normally, and then, after a few seconds (by which I would have started working on the code again), the 'updating vscode window' comes up and forcibly recloses vscode.
This seems to be an issue with the auto-update which occurs when vsc is closed, which I don't mind. Yet I think it should check if VSCode was reopened before forcing it to close.
So in essence I end up:
- close vsc
- re-open vsc immediately to continue working
- start working on the code which I restarted for
- after few seconds, vsc forcibly shut by the update window
- have to reopen vscode once again after the update
VS Code version: Code - Insiders 1.56.0-insider (5500358, 2021-04-02T05:15:44.248Z)
OS version: Windows_NT x64 10.0.19042
System Info
| Item |
Value |
| CPUs |
AMD Ryzen 5 2600 Six-Core Processor (12 x 3850) |
| GPU Status |
2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) |
undefined |
| Memory (System) |
15.95GB (4.91GB free) |
| Process Argv |
--crash-reporter-id 747316f3-3778-4cb6-876a-16368b07576d |
| Screen Reader |
no |
| VM |
0% |
Extensions (29)
| Extension |
Author (truncated) |
Version |
| pug |
ama |
1.0.1 |
| path-intellisense |
chr |
2.3.0 |
| bracket-pair-colorizer |
Coe |
1.0.61 |
| vscode-eslint |
dba |
2.1.19 |
| python-extension-pack |
don |
1.6.0 |
| vsc-material-theme |
Equ |
33.1.2 |
| vsc-material-theme-icons |
equ |
1.2.2 |
| todo-tree |
Gru |
0.0.209 |
| vscode-sshfs |
Kel |
1.20.0 |
| kite |
kit |
0.142.0 |
| MagicPython |
mag |
1.1.0 |
| rainbow-csv |
mec |
1.8.1 |
| anaconda-extension-pack |
ms- |
1.0.1 |
| python |
ms- |
2021.3.680753044 |
| vscode-pylance |
ms- |
2021.3.4 |
| jupyter |
ms- |
2021.5.702919634 |
| remote-wsl |
ms- |
0.54.6 |
| cmake-tools |
ms- |
1.6.0 |
| cpptools |
ms- |
1.2.2 |
| gremlins |
nho |
0.26.0 |
| autodocstring |
njp |
0.5.4 |
| platformio-ide |
pla |
2.3.1 |
| vscode-yaml |
red |
0.17.0 |
| swdc-vscode |
sof |
2.5.11 |
| cmake |
twx |
0.0.17 |
| vscode-counter |
uct |
2.2.2 |
| vscodeintellicode |
Vis |
1.2.12 |
| vscode-import-cost |
wix |
2.15.0 |
| html-css-class-completion |
Zig |
1.20.0 |
(1 theme extensions excluded)
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
pythonvsnew554:30265444
pythontb:30258533
pythonvspyt943:30277000
wslfolderdoc:30278405
vscoresta800:30283263
vspre833cf:30267465
pythonptprofiler:30281269
vsdfh931:30280409
vscnewfilebuttoncf:30280635
vshan820cf:30276953
vscoreces:30283204
pythondataviewer:30283452
Issue Type: Bug
I often have to restart vscode when things get stuck (not the issue).
I am encountering an issue where after I close and reopen vscode (without waiting a bit), vscode starts normally, and then, after a few seconds (by which I would have started working on the code again), the 'updating vscode window' comes up and forcibly recloses vscode.
This seems to be an issue with the auto-update which occurs when vsc is closed, which I don't mind. Yet I think it should check if VSCode was reopened before forcing it to close.
So in essence I end up:
VS Code version: Code - Insiders 1.56.0-insider (5500358, 2021-04-02T05:15:44.248Z)
OS version: Windows_NT x64 10.0.19042
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (29)
(1 theme extensions excluded)
A/B Experiments