CPU ran into 200%+ in VSCode 1.18.0

Question

CPU ran into 200%+ in VSCode 1.18.0

gonghao opened this issue 7 years ago · 29 comments

gonghao commented 7 years ago

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

Answer 1 · 2017-11-09T07:12:40.000Z

On Windows 10, the same happens.

Answer 2 · 2017-11-09T11:28:18.000Z

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

Answer 3 · 2017-11-09T16:07:09.000Z

Yep. Same on High Sierra, also on VSCode Insiders

Answer 4 · 2017-11-09T19:25:42.000Z

Same occurs on macOS 10.12.6

Answer 5 · 2017-11-10T04:58:55.000Z

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.

Answer 6 · 2017-11-10T14:28:31.000Z

@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.

Answer 7 · 2017-11-10T14:41:10.000Z

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.

Answer 8 · 2017-11-10T17:03:47.000Z

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

Answer 9 · 2017-11-10T17:06:35.000Z

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!

Answer 10 · 2017-11-10T17:15:47.000Z

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

Answer 11 · 2017-11-10T17:20:07.000Z

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

Answer 12 · 2017-11-10T22:21:19.000Z

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

Answer 13 · 2017-11-11T11:58:54.000Z

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

Answer 14 · 2017-11-11T18:31:48.000Z

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

Answer 15 · 2017-11-12T10:38:21.000Z

same for me on macOS 10.11.6 and vscode 1.18.

Answer 16 · 2017-11-14T01:45:04.000Z

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.

Answer 17 · 2017-12-03T18:07:56.000Z

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.

Answer 18 · 2018-03-08T20:37:30.000Z

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

Answer 19 · 2018-03-27T10:50:04.000Z

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

Answer 20 · 2018-03-27T20:40:47.000Z

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

Answer 21 · 2019-06-07T23:43:23.000Z

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

Answer 22 · 2019-07-02T08:13:38.000Z

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.

Answer 23 · 2020-03-02T22:27:16.000Z

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

Answer 24 · 2021-02-07T09:26:21.000Z

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

Answer 25 · 2021-05-20T16:48:24.000Z

@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:

Answer 26 · 2022-05-29T02:25:25.000Z

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.

Answer 27 · 2022-05-29T11:14:08.000Z

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.

Answer 28 · 2023-08-08T20:09:58.000Z

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.

Answer 29 · 2023-08-08T20:16:53.000Z

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).