Vs code is stuck at 'Activating Extensions...' when vim commands are typed in status bar
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Type: Bug
I installed vim(vscodevim) extension. earlier it used to work properly. But in recent times, VS Code is stuck at 'Activating Extensions...' in status bar and after sometime, extension is not activated. vim is always staying in 'NORMAL' mode and typing ':', '/' or any other command that turns mode to either 'INSERT' or 'COMMAND' mode is failing. This is happening especially in remote sessions and not in local sessions.This issue is happening like 90% of the times in recent days. I tried restarting VS Code, restarting system. None of them are working. I have to close and open VS Code like 10 to 15 times to get this working.
Extension version: 1.25.2
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 3.10.0-1160.92.1.el7.x86_64
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112) |
| 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 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.78GB (4.61GB free) |
| Process Argv | --crash-reporter-id ff83dda3-4ade-48c2-b0c0-efe40f3fb70e |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: ***********-vm |
| OS | Linux x64 3.10.0-1160.92.1.el7.x86_64 |
| CPUs | Intel(R) Xeon(R) Gold 6242R CPU @ 3.10GHz (16 x 3092) |
| Memory (System) | 47.17GB (29.29GB free) |
| VM | 100% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30792226
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
282f8724:30602487
89544117:30613380
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the activation failure using VS Code 1.81.1, Vim 1.25.2, and a remote SSH session with the versions listed in the report. Trace the extension activation path and compare remote and local behavior; done means Vim activates reliably and commands such as ':' and '/' leave NORMAL mode without leaving VS Code stuck at 'Activating Extensions...'.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100