VSCode windows not staying in their respective virtual desktops on app restart
See original GitHub issueIssue Type: Bug
Open an arbitrary number of VSCode windows. Split them randomly among a number of virtual desktops. Restart VSCode All windows open in the same virtual desktop
I’m on W11 (can’t recall wether this happened in W10 too). Quite annoying, specially because the new W11 virtual desktop UI lags tremendously on my PC, meaning each time I have to re-move the VSCode windows to the virtual desktops I want them in I can spend 5 minutes doing so.
A plethora of other apps follow the expected behaviour: Sublime text Edge RStudio Visual Studio etc
VS Code version: Code - Insiders 1.67.0-insider (f050b17dacedba13962244b13c70084a473d08f7, 2022-04-06T05:15:56.751Z) OS version: Windows_NT x64 10.0.22000 Restricted Mode: No Remote OS version: Linux x64 5.4.0-1059-aws
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i5-1035G1 CPU @ 1.00GHz (8 x 1190) |
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 oop_rasterization: enabled 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 |
Load (avg) | undefined |
Memory (System) | 11.70GB (1.86GB free) |
Process Argv | –crash-reporter-id 4285aea8-8024-49ba-97f2-9d60622a70f0 |
Screen Reader | no |
VM | 0% |
Item | Value |
---|---|
Remote | SSH: AWS |
OS | Linux x64 5.4.0-1059-aws |
CPUs | Intel® Xeon® Platinum 8259CL CPU @ 2.50GHz (8 x 3195) |
Memory (System) | 30.91GB (0.69GB free) |
VM | 0% |
Extensions (11)
Extension | Author (truncated) | Version |
---|---|---|
jupyter-keymap | ms- | 1.0.0 |
remote-containers | ms- | 0.232.3 |
remote-ssh | ms- | 0.78.0 |
remote-ssh-edit | ms- | 0.80.0 |
remote-wsl | ms- | 0.66.0 |
vscode-remote-extensionpack | ms- | 0.21.0 |
python | ms- | 2022.4.0 |
vscode-pylance | ms- | 2022.3.4 |
jupyter | ms- | 2022.4.1000971004 |
jupyter-keymap | ms- | 1.0.0 |
jupyter-renderers | ms- | 1.0.6 |
(2 theme extensions excluded)
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vsdfh931:30280409
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30449409
pythonvspyt640:30438691
vscscmwlcmt:30465136
pynewfile477:30451556
Issue Analytics
- State:
- Created a year ago
- Reactions:18
- Comments:5 (1 by maintainers)
Top GitHub Comments
This issue has been a major reason for me to avoid installing new updates more than once a month. With many windows across multiple virtual desktops, closing and restoring everything all at once is a real pain. I have to take stock of what windows I have where before letting VS Code reload, so that I can then manually move the windows back to the appropriate desktops.
I’ll also add to the list: Google Chrome does this correctly.
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!