Input freezes on typing

[idoo]

Vim mode doesn't allow to type text

To Reproduce
Steps to reproduce the behaviour:

1. Open any file
2. Switch to insert mode
3. Type something
4. VIM mode freeze and don't type anything and it's not possible to exit from input mode

Expected behaviour
Allow to type text

• Extension (VsCodeVim) version:
• VSCode version: Version 1.35.0 (1.35.0)
• OS: OSX 10.14.5 (18F203)

Do you have ideas about how I could debug it and catch why it happens?

[Georacer]

I have the same issue, which appears when:

1. I use the doxygen documentation generator extension
2. Go into Insert mode
3. Hit the comment block initiation sequence.

VSCode version: 1.35.0
OS: Ubuntu 18.04

[idoo]

@Georacer I don't have doxygen btw

It happens with any kind of files — even plain HTML

[rcarmo]

I have the same (randomly occurring) issue. It's been bugging me for a while, and it took me a bit to make sure it was this extension. I usually toggle vim mode to resume working, but it can take a few seconds to do so and is extremely irritating when it happens.

[wldcordeiro]

I'm positive this extension is just a giant memory leak because of its action history. It starts running just fine but after ~1 hour of usage it always slows to a crawl.

[rcarmo]

I’ve switched to amVim in the meantime. It does less, but has given me zero hassles and is a smaller codebase that I can read in one sitting.

[idoo]

@rcarmo amVim does not support a lot of keycomb — for example, change surrounds

[wldcordeiro]

It doesn't completely halt the editor though which is 100x more important than features. Editing should never have freezes.

[jwmann]

I'm also getting this issue.
Don't have doxygen either.

Happened when vscode updated to 1.36.0
Could be a coincidence though.

[jwmann]

After a system restart, I'm still getting this issue.
It seems to happen even when visually selecting text.

My theory is that it's based on the status bar changing but I could be wrong.

[jwmann]

As I suspected above, it seems to be related to the status bar switching.
Setting "vim.statusBarColorControl": false, in my settings.json will alleviate any hang for me.

Let me know if this works for you too.

[smlparry]

@jwmann thanks so much! That fixed it for me 🔥 I guess its related to the updates in the latest release of vs code

[idoo]

I had such parameter switched off btw, so keeping looking

[elonliu]

Same issue here. By turning off vim.statusBarColorControl seems to work.
I noticed recently VS Code is updated with a feature that supports individual on/off settings for each status bar element. Not knowing if there's a connection.

[loisgomez]

Same issue here. I've been getting editor slow downs and freezes continuously while using vim.statusBarColorControl. Disabling this feature has solved the issue for me too.

[claforte]

Same problem in one Python file, not particularly big (417 lines), at a particular line:

    assert len(str(pm4_folder_path)) < 200 # Windows still doesn't properly support paths longer than 225 characters. WTF it's 2019 for god's sake!

Disabling vim.statusBarColorControl made no difference.

I could confidentially share the source file with a trusted party (e.g. Microsoft) if needed. Let me know.

[tanc]

Also having this problem when editing (some) class names in insert mode in html documents. Have to restart vscode each time. Disabling vim.statusBarColorControl also made no difference.

[yesudeep]

This is still a problem if someone can take a look at it.