VSCodeVim / VSCodeVim/Vim

Code Helper uses 99% CPU when Auto Close Tag plugin is used with VSCodeVim

Open
#2,119 1 comment 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/performance
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

  • Click thumbs-up 👍 on this issue if you want it!
  • Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.


Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG
Environment:

  • VSCode Version: 1.17.2
  • VsCodeVim Version: 0.10.2
  • OS: OS X El Capitan 10.11.6

What happened:

Start typing a closing tag and let Auto Close Tag trigger drop down of autocompletions. Eg, Type

<v-dialog></...

The options will show in a drop down but then VSCode becomes immediately unresponsive. I bring up Mac's Activity Monitor and see "Code Helper" at 99% CPU. Force quitting Code Helper alleviates the issue but it will happen each time you reproduce the steps.

Auto Close Tag works fine withVSCodeVim plugin disabled.

What did you expect to happen:
Using VSCodeVim and Auto Close Tag plugin to work together without crashing VSCode.

How to reproduce it:
Install VSCodeVim and Auto Close Tag plugins. Open an HTML file and type any HTML tag and then start typing its corresponding closing tag. Let autocomplete options show and observe activity monitor for CPU usage.

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 installing VSCodeVim and Auto Close Tag in VS Code, opening an HTML file, and reproducing the closing-tag autocomplete case while watching Activity Monitor. Compare the behavior with VSCodeVim disabled; done means both extensions can be enabled without Code Helper becoming unresponsive or reaching about 99% CPU.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.