microsoft / microsoft/vscode-remote-release

Extension takes a long time to activate

Open
#11,661 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Type: Performance Issue

Launch vscode; click on Remote Explorer tab on the left bar; the Remote Explorer tab takes > 3 minutes to load and show my remote hosts configured in .ssh/config. During the wait, VSCode shows "activating extension" and a loading icon.

Extension version: 0.123.0
VS Code version: Code 1.121.0 (Universal) (f6cfa2ea2403534de03f069bdf160d06451ed282, 2026-05-19T11:51:53+02:00)
OS version: Darwin arm64 25.5.0
Modes:
Remote OS version: Linux x64 5.15.0-139-generic
Remote OS version: Linux x64 5.15.0-139-generic

System Info
Item Value
CPUs Apple M4 (10 x 2400)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x106b [Google Inc. (Apple)], DEVICE=0x0000 [ANGLE (Apple, ANGLE Metal Renderer: Apple M4, Version 26.5 (Build 25F71))], DRIVER_VENDOR=Apple, DRIVER_VERSION=26.5 ACTIVE
Machine model name: Mac
Machine model version: 16.13
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
skia_graphite: enabled_on
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 3, 2, 3
Memory (System) 24.00GB (0.09GB free)
Process Argv --crash-reporter-id 946e31a3-9d16-41f3-87fa-939fc2740a7d
Screen Reader no
VM 0%
Item Value
Remote SSH: spur
OS Linux x64 5.15.0-139-generic
CPUs AMD EPYC 9454 48-Core Processor (96 x 1517)
Memory (System) 251.40GB (242.30GB free)
VM 0%
Item Value
Remote SSH: spur
OS Linux x64 5.15.0-139-generic
CPUs AMD EPYC 9454 48-Core Processor (96 x 1495)
Memory (System) 251.40GB (242.32GB free)
VM 0%
Process Info
CPU %	Mem MB	   PID	Process
    8	82331430688	 20494	code
    3	31665934880	 20497	   gpu-process
    0	18999560928	 20498	   utility-network-service
    0	50665495808	 20539	shared-process
    0	     0	 26429	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	132996926496	 20724	window [2] (bfs_warmup_sweep.ipynb — vectordb-baselines [SSH: spur])
    0	56998682784	 26204	extension-host [2]
    0	18999560928	 26246	     electron-nodejs (localServer.js)
    0	     0	 26257	       ssh -v -T -D 53873 -o ConnectTimeout=60 spur
    0	18999560928	 26229	file-watcher [2]
    7	183662422304	 26267	window [3] (inplace_backend.h — vectordb-bench [SSH: spur])
    0	50665495808	 26300	   window
    0	25332747904	 26322	pty-host
    0	56998682784	 26328	extension-host [3]
    0	18999560928	 26338	file-watcher [3]
Connection to 'ssh-remote+spur' could not be established
Connection to 'ssh-remote+spur' could not be established
Workspace Info

Connection to 'ssh-remote+spur' could not be established
Connection to 'ssh-remote+spur' could not be established;
A/B Experiments
vsliv368:30146709
vswsl492:30256859
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
63221493:31336333
envsactivate1:31505457
cloudbuttont:31379625
3efgi100_wstrepl:31403338
ec5jj548:31422691
cp_cls_t_966_ss:31454198
inlinechat_v2_hd992725:31505030
8hhj4413:31478653
38bie571_auto:31426784
cp_cls_t_1081:31454832
conptydll_true:31498968
e9c30283:31461165
test_treatment2:31471001
c9b86496:31447327
idci7584:31464702
e3e4d672:31494082
ei9d7968:31496641
chat:31457767
haiku_b88ai751:31519606
7e187181:31503455
ghj88844:31499326
ddid_c:31478207
hmra_i5g22:31518061
getcmakediagnosticson:31489824
7df3h592:31512476
cp_cls_t_1082:31516087
logging_enabled_new:31498466
db5d2638:31499441
jb_cp_cls_c_632:31517842
56dj4588:31512888
cg448276_tst_on:31514358
32d76977:31512328
ha629193:31508444
539gd155_c:31506875
jh5f2457_c:31515489
61138546:31518536

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the delay with VS Code 1.121.0 and extension 0.123.0: launch VS Code, open Remote Explorer, and observe activation while hosts from .ssh/config load. The report names no source file or test, so identify the activation path responsible for loading remote hosts and verify that Remote Explorer loads without the reported multi-minute wait.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.