Vim
Vim copied to clipboard
Navigation unresponsive on large files
Describe the bug Hi, I noticed that when I open a large file (I have a JSON lines file that contains over 650k lines and is close to 900MB in size) the extension makes VSCode unresponsive to navigation and editing. I cannot move caret with h/j/k/l or arrow keys and I cannot toggle insert mode on. The problem goes away when I disable the extension.
I checked the open issues but I saw only issues related to slowness when opening large files but even larger files makes the extension unusable totally. Is this a known issue and is there a workaround?
To Reproduce Steps to reproduce the behavior:
- Open a large file
- Try to navigate or switch to insert mode by pressing
i
- VSCode/vim-extension seems to be unresponsive
Expected behavior Navigation and editing the file would work.
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.20.2
- VSCode version: 1.55.2
- OS: macOS Big Sur 11.3.1
Same here. Only just started happening.
I've started seeing this as well. I get it on relatively small files. It's a ruby source file containing a multiline array and many of the lines are commented.
When vscode freezes, all keyboard input in the editor is blocked, but I can use the mouse to switch tabs, and scroll around. Running top
in terminal shows me that CodeHelper
is using all resources. Doing a kill -9
on that process frees things up again, and VSCode reports the failure and asks if the helper should be restarted. I say yes, it does it, and I get another 45 mins of coding done before it happens again.
I'm afraid I can't tell if it's the Vim extension or just VSCode itself.
Is there any solution?
Is there any solution?
I found no solution, and it's still happening for me.
Reproduced, Editor becomes unresponsive to anything but mouse input.
VsVim ver: 1.21.10 system: Ubuntu 20.04.2 kernel - 5.11.0-44 vscode ver: 1.62.3
same here.
Me too. Been experiencing this for a while. At this point, I have to disable VSCodeVim, because this happens too frequently.
Some way to fix it? or at least improve it?
What worked for me was disabling a large number of extensions. Then, I re-enabled them slowly. In the end, I'm not sure which one was causing the issue. I did not re-enable all of them.
Recently started facing this issue. Weird thing is previously it worked perfectly, but now it just completely stops working when I open a json lines file