bug: constant random CPU 100 with M1 MBP

[TeemuKoivisto]

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

Version: 1.95.3
Commit: f1a4fb1
Date: 2024-11-13T14:50:04.152Z (1 wk ago)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0

Description:

So about 6 months ago(?) or so, I started noticing that my laptop felt surprisingly warm on my lap. Peeking at htop, I noticed VSCode had suddenly hogged a CPU core and was using it at 100%. Odd, I thought, but considered it as a one-off fluke. "They'll fix it with a new version." Now, 6 versions later (I can't recall exactly when this started), this problem persists and is getting more annoying by the day, as I have to keep watching my htop panel and killing off any erratic processes by hand.

I just turned off all the extensions and rebooted VSCode, and it immediately caused 2 CPUs to go to 100. I think this might be related to the TS type checking as on occasion that this has happened, intellisense has as well stopped working.

But since I'm not completely sure, could someone point out to me how I can reliably see & track what makes my VSCode go haywire? I've inspected the process name from htop but it seemed like an ordinary VSCode prosess. I can copy-paste it here once it happens again, but better debugging commands could be useful.

Steps to Reproduce:

1. Start VSCode
2. As I edit TS, at some point a CPU starts hogging 100% of resources

[gjsjohnmurray]

Maybe #232699 (comment) is relevant.

Are you able to test with 1.96 Insiders?

[TeemuKoivisto]

Maybe #232699 (comment) is relevant.

Are you able to test with 1.96 Insiders?

Thanks, that thread looks a lot like what I have been experiencing. I'll try the 1.96. But this will come to mainline in week or so? I'll keep this issue updated.

[gjsjohnmurray]

1.96 will probably ship to everyone a bit over 2 weeks from now.