CPU ran into 200%+ in VSCode 1.18.0 #2124

gonghao · 2017-11-09T04:00:54Z

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 REPORT

Environment:

VSCode Version: 1.18.0
VsCodeVim Version: 0.10.2
OS: macOS 10.13.2 Beta (17C67b)

What happened:

When I upgrade to VSCode 1.18.0 the CPU ran into extreme high, I found it caused by two Code Helper.app processes. Then I just disabled all extensions, everything is OK. It is clear that this issues is caused by extensions conflicts with VSCode, so I re-enabled each extension to figure out which one caused this situation. Finally I found it is VSCodeVim, I just re-enabled every other extensions everything is OK, but after re-enable VSCodeVim, the CPU went high.

So I don't know do you guys have the same issue?

What did you expect to happen:

Normal CPU usage.

How to reproduce it:

Install VSCode 1.18.0
Install VSCodeVim and enabled it

The text was updated successfully, but these errors were encountered:

francescarpi · 2017-11-09T07:12:40Z

On Windows 10, the same happens.

ivanvoznyakovsky · 2017-11-09T11:28:18Z

Same on High Sierra 10.13. Opening a file creates 2 CodeHelper processes with 100%+ CPU usage.

MythicalFish · 2017-11-09T16:07:09Z

Yep. Same on High Sierra, also on VSCode Insiders

stevestmartin · 2017-11-09T19:25:42Z

Same occurs on macOS 10.12.6

colbell · 2017-11-10T04:58:55Z

I've got the same problem on Ubuntu 17.10.

I disabled "Easy motion", I.E added "vim.easymotion": false, to the user settings file, restarted VS Code and opened a Ruby source file. Once the "indexing ruby source" finishes the CPU dropped away.

So it looks like an issue with "Easy Motion".

Ignore the above. It hasn't fixed it. The CPU stays down until you start moving the cursor around in the source file, once you do that the CPU rises again and stays up.

Last Attempt

I open the User settings and quit VS Code. Then start it up again, open my Ruby source file and start editing, everything is fine, CPU is low. Play around for a while, quit and restart. Now the problem starts again.

It seems that if VS Code has a source file active when it starts up then the problem occurs but if you start it up with the user settings as the active pane and then open a source file you are ok.

Can anybody else confirm this behaviour or am I going slightly crazy- its been a long day.

stevestmartin · 2017-11-10T14:28:31Z

@colbell confirmed, if I open it with any source file active even a blank one CPU usage spikes, if i open the user settings tab and relaunch CPU is low. I can consistently reproduce this, switching to a source code tab after launch, or having source code tabs open (regardless of tab order) at launch CPU still remains low, it seems this occurs only when a source code based tab has focus on launch.

ivanvoznyakovsky · 2017-11-10T14:41:10Z

I have my CPU going crazy whenever a file is focused or vscode is re-open with a prev file opened. once I have any file opened CPU usage spikes.

adamwiggall · 2017-11-10T17:03:47Z

Same for me on Sierra 10.12.6, running VS code 1.18.0.

jondot · 2017-11-10T17:06:35Z

Have the same thing. Arrived at Vim extension by elimination of extensions. Profiled the extension and got this:

Which hints at my customising the status bar colors. Removed my config and everything is normal again!

stevestmartin · 2017-11-10T17:15:47Z

Disabling custom status bar colors corrected the problem for me also.

gonghao · 2017-11-10T17:20:07Z

@jondot Great job! I just disabled the customize status bar colors, everything goes well!

colbell · 2017-11-10T22:21:19Z

Nice one @jondot disabling the colours fixed it for me too.

ivanvoznyakovsky · 2017-11-11T11:58:54Z

confirm that "vim.statusBarColorControl": false fixes the issue. great catch @jondot 👍
don't think it's a real fix but rather a workaround 😄

chasestarr · 2017-11-11T18:31:48Z

I can reproduce consistently on Version 1.18.

Just tested in Version 1.19.0-insider 11-11-17 on MacOS Sierra 10.12.5 and cannot reproduce CPU spike.

@MythicalFish can you still repro? I can't find a PR relevant to this issue landing in vscode from the past few days - which I find strange https://github.com/Microsoft/vscode/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20closed%3A%3E2017-11-07

samumist · 2017-11-12T10:38:21Z

same for me on macOS 10.11.6 and vscode 1.18.

newro · 2017-11-14T01:45:04Z

I am experiencing a phenomenon that the CPU becomes higher after vscode 1.18 update in the Win10 environment.
The code helper process is using a high CPU, and disabling the vim plugin disables the symptom.

sc0ttwad3 · 2017-12-03T18:07:56Z

It was the vim extension causing the 100% CPU usage issue for me also. Removing any/all "neovim" related settings took care of the problem. Just changing some to a 'disabled' value or just commenting out did not work. I had to totally remove then entries.

Chillee · 2018-03-08T20:37:30Z

Does anybody still get this issue on recent versions of VSCodeVim?

bas72 · 2018-03-27T10:50:04Z

I still experienced this issue in 1.21.1 and for me it was fixed by commenting out the "vim.disableAnnoyingNeovimMessage" setting.

jpoon · 2018-03-27T20:40:47Z

@stevebasford that setting is deprecated, it was removed awhile ago. Closing this issue as it seems resolved.

ChasKane · 2019-06-07T23:43:23Z

I was brought here by the below link (about 2/3 of the way down the page, in the emulated-plugins section), thinking I couldn't use vim-airline with VSCodeVim. It seems this no longer affecting vim-airline, yes? Might be best to remove the disclaimer at the top of the emulated-plugins section

https://marketplace.visualstudio.com/items?itemName=vscodevim.vim#-emulated-plugins

xelaos · 2019-07-02T08:13:38Z

From my experience it depends on the machine you are using. Maybe it was worse in 2017 regardless of your machine, but it is still an issue.

andyearnshaw · 2020-03-02T22:27:16Z

I'd recommend sticking a 👍 on microsoft/vscode#43226 if you want to be able to enable statusbar colours without performance issues.

nzig · 2021-02-07T09:26:21Z

Could this recent change solve this?
https://code.visualstudio.com/updates/v1_53#_status-bar-entry-background-color-api

The-Compiler · 2021-05-20T16:48:24Z

@nzig that blog post says:

Currently only statusBarItem.errorBackground is supported to avoid the Status bar looking too colorful.

so it looks to me like that'd be of limited use...

FWIW I managed to find a solution to color the status bar item based on its text, using the Customize UI extension:

    "customizeUI.stylesheet": {
        "#vscodevim\\.vim\\.primary[aria-label=\"-- INSERT --\"]": "background-color: #98971a !important;",
        "#vscodevim\\.vim\\.primary[aria-label=\"-- VISUAL --\"]": "background-color: #b16286 !important;",
        "#vscodevim\\.vim\\.primary[aria-label^=\":\"]": "background-color: #7c6f64 !important;",
    },

result:

edgartaor · 2022-05-29T02:25:25Z

FWIW I managed to find a solution to color the status bar item based on its text, using the Customize UI extension:

For some reason this does not work for me. How do you find those values ("#vscodevim\..."). Maybe those are different now.

The-Compiler · 2022-05-29T11:14:08Z

FWIW I managed to find a solution to color the status bar item based on its text, using the Customize UI extension:

For some reason this does not work for me. How do you find those values ("#vscodevim..."). Maybe those are different now.

They are indeed! It's #vscodevim\\.vim\\.primary now, adjusted above.

I found them by opening the developer tools (Ctrl-Shift-P, "Developer: Toggle Developer tools") and then using the picker at the top left of the "Elements" tab to inspect the element.

robertfw · 2023-08-08T20:09:58Z

FYI, Customize UI no longer works so that option is off the table :(

I'd love to get something along these lines, as I'm often not noticing which mode I'm in, even with different cursors for insert vs normal.

The-Compiler · 2023-08-08T20:16:53Z

FYI, Customize UI no longer works so that option is off the table :(

I switched to be5invis/vscode-custom-css which still works (though since the CSS is placed in a normal file with it, use \ instead of \\ and " instead of \" above).

johnnybakucz · 2024-07-16T15:22:44Z

FYI, Customize UI no longer works so that option is off the table :(

I switched to be5invis/vscode-custom-css which still works (though since the CSS is placed in a normal file with it, use \ instead of \\ and " instead of \" above).

I seriously love your solution, I modified it a bit to color the whole status bar to make it more visible of a change.

    #workbench\.parts\.statusbar:has([aria-label="-- NORMAL --"]) {
        background-color: #27981a !important;
    }

    #workbench\.parts\.statusbar:has([aria-label="-- INSERT --"]) {
        background-color: #de080f !important;
    }

    #workbench\.parts\.statusbar:has([aria-label="-- VISUAL --"]) {
        background-color: #8362b1 !important;
    }

    #workbench\.parts\.statusbar:has([aria-label="-- VISUAL LINE --"]) {
        background-color: #62b1b1 !important;
    }

raulpenate · 2024-09-12T12:27:47Z

An easy alternative solution is to install and give permissions to Apc Customize UI++ and add the following to settings.json:

{
  "apc.stylesheet": {
    /* Default footer style */
    ".part.statusbar.status-border-top": "background-color: rgb(143, 188, 187); color: rgb(67, 76, 94);",
    /* Apply styles based on aria-label in the footer */
    ".part.statusbar.status-border-top [aria-label='-- NORMAL --']": "background-color: #8FBCBB; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- INSERT --']": "background-color: #BF616A; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- VISUAL --']": "background-color: #B48EAD; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- VISUAL LINE --']": "background-color: #B48EAD; color: #434C5E;"
  }
}

its-Danial · 2024-09-19T16:55:29Z

An easy alternative solution is to install and give permissions to Apc Customize UI++ and add the following to settings.json:

{
  "apc.stylesheet": {
    /* Default footer style */
    ".part.statusbar.status-border-top": "background-color: rgb(143, 188, 187); color: rgb(67, 76, 94);",
    /* Apply styles based on aria-label in the footer */
    ".part.statusbar.status-border-top [aria-label='-- NORMAL --']": "background-color: #8FBCBB; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- INSERT --']": "background-color: #BF616A; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- VISUAL --']": "background-color: #B48EAD; color: #434C5E;",
    ".part.statusbar.status-border-top [aria-label='-- VISUAL LINE --']": "background-color: #B48EAD; color: #434C5E;"
  }
}

Really helpful answer, because I belive if you use the "vim.statusBarColorControl" option then you cannot use "extensions.experimental.affinity" correctly because it keeps updating the settings.json.

I added a few things to your settings hope it helps, feel more complete now.

  "apc.stylesheet": {
    /* Apply styles based on aria-label in the footer */
    "#vscodevim\\.vim\\.primary": "padding: 0 4px;",
    "#vscodevim\\.vim\\.primary[aria-label='Already at oldest change']": "background-color: #475569; color: #d1d5db;",
    "#vscodevim\\.vim\\.primary[aria-label^='-- NORMAL']": "background-color: #8FBCBB; color: #434C5E;",
    "#vscodevim\\.vim\\.primary[aria-label='-- INSERT --']": "background-color: #BF616A; color: #e5e7eb;",
    "#vscodevim\\.vim\\.primary[aria-label='-- VISUAL --'], #vscodevim\\.vim\\.primary[aria-label='-- VISUAL LINE --']": "background-color: #B48EAD; color: #e5e7eb;",
    "#vscodevim\\.vim\\.primary[aria-label='-- VISUAL BLOCK --']": "background-color: #A3BE8C; color: #434C5E;",
    "#vscodevim\\.vim\\.primary[aria-label='-- REPLACE --']": "background-color: #D08770; color: #434C5E;",
    "#vscodevim\\.vim\\.primary[aria-label='-- EASYMOTION INPUT --'], #vscodevim\\.vim\\.primary[aria-label='-- SURROUND INPUT --']": "background-color: #007ACC; color: #e5e7eb;",
    "#vscodevim\\.vim\\.primary[aria-label^=':'], #vscodevim\\.vim\\.showcmd": "color: #fafafa;"
  }

jpoon added the area/performance label Nov 14, 2017

houkanshan mentioned this issue Nov 17, 2017

CPU usage high and status bar flickers when works with VSCode Vim streetsidesoftware/vscode-spell-checker#153

Closed

westim mentioned this issue Nov 22, 2017

statusBarColorControl option is using 100% of CPU #2166

Closed

lionsole mentioned this issue Nov 23, 2017

High Memory Usage(Over 3GB) microsoft/vscode#37913

Closed

jpoon mentioned this issue Nov 29, 2017

High CPU usage when opening any file #2176

Closed

ghost mentioned this issue Dec 5, 2017

Enabling vscodevim causes 30% spike in CPU usage #2195

Closed

jpoon closed this as completed Mar 27, 2018

crucialfelix mentioned this issue Jul 9, 2018

Typing has gotten very slow, probably due to large files microsoft/vscode#53859

Closed

Kynolin mentioned this issue Aug 22, 2018

VSCodeVim airline affecting color scheme #2948

Closed

Delapouite mentioned this issue May 12, 2020

Stronger visual indication of Normal mode in status bar johtela/vscode-modaledit#13

Closed

jeslinmx mentioned this issue Nov 21, 2023

Status Bar *Item* Color Control #8741

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CPU ran into 200%+ in VSCode 1.18.0 #2124

CPU ran into 200%+ in VSCode 1.18.0 #2124

gonghao commented Nov 9, 2017

francescarpi commented Nov 9, 2017 •

edited

Loading

ivanvoznyakovsky commented Nov 9, 2017 •

edited

Loading

MythicalFish commented Nov 9, 2017

stevestmartin commented Nov 9, 2017

colbell commented Nov 10, 2017 •

edited

Loading

stevestmartin commented Nov 10, 2017

ivanvoznyakovsky commented Nov 10, 2017

adamwiggall commented Nov 10, 2017

jondot commented Nov 10, 2017

stevestmartin commented Nov 10, 2017

gonghao commented Nov 10, 2017 •

edited

Loading

colbell commented Nov 10, 2017

ivanvoznyakovsky commented Nov 11, 2017

chasestarr commented Nov 11, 2017

samumist commented Nov 12, 2017

newro commented Nov 14, 2017

sc0ttwad3 commented Dec 3, 2017

Chillee commented Mar 8, 2018

bas72 commented Mar 27, 2018 •

edited

Loading

jpoon commented Mar 27, 2018

ChasKane commented Jun 7, 2019

xelaos commented Jul 2, 2019

andyearnshaw commented Mar 2, 2020

nzig commented Feb 7, 2021

The-Compiler commented May 20, 2021 •

edited

Loading

edgartaor commented May 29, 2022

The-Compiler commented May 29, 2022

robertfw commented Aug 8, 2023

The-Compiler commented Aug 8, 2023

johnnybakucz commented Jul 16, 2024

raulpenate commented Sep 12, 2024

its-Danial commented Sep 19, 2024 •

edited

Loading

CPU ran into 200%+ in VSCode 1.18.0 #2124

CPU ran into 200%+ in VSCode 1.18.0 #2124

Comments

gonghao commented Nov 9, 2017

francescarpi commented Nov 9, 2017 • edited Loading

ivanvoznyakovsky commented Nov 9, 2017 • edited Loading

MythicalFish commented Nov 9, 2017

stevestmartin commented Nov 9, 2017

colbell commented Nov 10, 2017 • edited Loading

stevestmartin commented Nov 10, 2017

ivanvoznyakovsky commented Nov 10, 2017

adamwiggall commented Nov 10, 2017

jondot commented Nov 10, 2017

stevestmartin commented Nov 10, 2017

gonghao commented Nov 10, 2017 • edited Loading

colbell commented Nov 10, 2017

ivanvoznyakovsky commented Nov 11, 2017

chasestarr commented Nov 11, 2017

samumist commented Nov 12, 2017

newro commented Nov 14, 2017

sc0ttwad3 commented Dec 3, 2017

Chillee commented Mar 8, 2018

bas72 commented Mar 27, 2018 • edited Loading

jpoon commented Mar 27, 2018

ChasKane commented Jun 7, 2019

xelaos commented Jul 2, 2019

andyearnshaw commented Mar 2, 2020

nzig commented Feb 7, 2021

The-Compiler commented May 20, 2021 • edited Loading

edgartaor commented May 29, 2022

The-Compiler commented May 29, 2022

robertfw commented Aug 8, 2023

The-Compiler commented Aug 8, 2023

johnnybakucz commented Jul 16, 2024

raulpenate commented Sep 12, 2024

its-Danial commented Sep 19, 2024 • edited Loading

francescarpi commented Nov 9, 2017 •

edited

Loading

ivanvoznyakovsky commented Nov 9, 2017 •

edited

Loading

colbell commented Nov 10, 2017 •

edited

Loading

gonghao commented Nov 10, 2017 •

edited

Loading

bas72 commented Mar 27, 2018 •

edited

Loading

The-Compiler commented May 20, 2021 •

edited

Loading

its-Danial commented Sep 19, 2024 •

edited

Loading