vscode: Activate/Focus from command line leaves VSCode stuck (Windows OS)
Issue Type: Bug
I’ve been seeing this a lot relatively recently (several weeks at least, probably months); although it’s intermittent, it happens frequently. I’ve reproduced it with all extensions disabled.
Sometimes when I invoke vscode from cmd.exe in windows (vscode is already running), when vscode comes to the foreground, it doesn’t open the requested file, and it’s stuck. As soon as I send it down and bring it back up again (alt-tab) the file opens and vscode is fine.
It’s gotten pretty tedious.
I’m invoking code through 2 layers of .cmd files, although I don’t think this has anything to do with it. e.cmd:
@for %%f in (%*) do @call c "%%f"
and c.cmd:
@"C:\Program Files\Microsoft VS Code\bin\code.CMD" %*
VS Code version: Code 1.61.2 (6cba118ac49a1b88332f312a8f67186f7f3c1643, 2021-10-19T14:57:20.575Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Xeon® CPU E3-1270 V2 @ 3.50GHz (8 x 3492) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.95GB (19.62GB free) |
| Process Argv | –disable-extensions . --crash-reporter-id 39bea185-078d-4173-a244-da107d90ee57 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30384385
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
vsccppwtct:30382698
bridge0708:30335490
pygetstartedt3:30385195
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200cf:30386380
vsaa593cf:30376535
vssld246:30386377
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (4 by maintainers)
I’d removed the
--disable-features=CalculateNativeWinOcclusionfrom my startup script in September 2022 based on #158260.Haven’t seen this behavior in a long time.