v1.87.2 CPU Usage

[totalhack]

Does this issue occur when all extensions are disabled?: Yes

Version: 1.87.2
Commit: 863d258
Date: 2024-03-08T15:14:59.643Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 6.5.0-1018-oem

Steps to Reproduce:

1. Open vscode.
2. Observe your CPU usage.

I just updated to 1.87.2 and this is new behavior. If I close vscode CPU usage drops to ~1-2%, with it open its hovering around 25% across all cores/threads.

[gjsjohnmurray]

Does the Start Extension Bisect command help you identify an extension causing this?

I just noticed you said that it happens with all extensions disabled.

[totalhack]

It happens with all extensions disabled. I downgraded to 1.85.2 and the issue goes away.

…

On Wed, Mar 27, 2024, 9:46 AM John Murray ***@***.***> wrote: Does the Start Extension Bisect command help you identify an extension causing this? — Reply to this email directly, view it on GitHub <#208902 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNI2RDOZAURVY3BR3IIMRTY2K5TJAVCNFSM6AAAAABFK2QY26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRSHAYTGMZWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[totalhack]

Note that the issue was still present when I downgraded to 1.86.2.

[msakrejda]

I'm also seeing similar behavior. Extension Bisect (what a cool feature! I did not know about it before) told me it was not an extension. Here's my Code info:

Version: 1.87.2
Commit: 863d258
Date: 2024-03-08T15:14:59.643Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 6.5.0-26-generic

(Notably, I'm also on Linux.)

For me, this happens when I engage completion features with Ctrl+Space. The CPU sits at ~100% for minutes and eventually comes down. Code is also using a terabyte (!) of virtual memory.

This seems to happen in my React code, but not in my Rails, Rust, or Go code.

[msakrejda]

Curiously, code-insiders also has the issue, but the interface remains usable (whereas code completion features hang on the release version when this happens).

Version: 1.88.0-insider
Commit: 9e0b3f3
Date: 2024-03-27T21:46:06.351Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-26-generic

[msakrejda]

I tried to add a performance trace as suggested here, but I seem to be running into this bug, which is only fixed in Electron 29.

[msakrejda]

I also tried downgrading to 1.85.2, as suggested above, and that also fixes the issue for me.

[msakrejda]

For what it's worth, I also started seeing the problem with 1.85.2. However, I rebooted my system and Code is now working fine. Idle CPU usage is minimal, and completions are responsive (once the system is initialized). I've upgraded back to 1.87.2, and things are still fine.

I think there's still something fishy here, since CPU usage was unreasonable and I don't think I did anything wrong to get into that state, but it's nice to know at least there's a workaround. If a reboot does not fix the original problem, maybe what I was seeing was only vaguely related. If that's the case, sorry for the noise; if the problem comes back, I might try to open a new issue.