-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
100%+ CPU usage from "Code Helper". #72002
Comments
Try There was an issue with styled components and the typescript issue that was causing this to occur. It helped fix the issue for some but not others. It's worth a shot. See #71886 for more info |
I added the suggested temp folder but still there's no change. |
the same issue happened on me, macOS 10.14.4, vscode 1.33.0, now I can only use the old version 1.32.3 and disabled the automatic update. Tried "files.watcherExclude" but nothing changed. |
Yes. Same here. Switched to an insiders build, works fine. |
A little additional info:
If there is a chance to see what changed with last update (i don't mean
changes overall, but to my instancje of vs studio- like a log/historyczne
what was added with update).
It all started with me updating VS Code.
śr., 10.04.2019, 10:41 użytkownik Benjamin Pasero <[email protected]>
napisał:
… [image: image]
<https://user-images.githubusercontent.com/900690/55864524-fb32e600-5b7c-11e9-8b13-096e0391cdec.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#72002 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AuAfgHBjgx_pu203cxvP2yCneF8d9w3gks5vfaOcgaJpZM4cktNQ>
.
|
Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions. Thanks. |
Hey all, I had the same issue after upgrading to version 1.33, but after letting the program run for a little while, the CPU usage is now back to normal. |
What if: |
Same issue(#67150) |
I'm having the same issue with Version 1.33.0 (1.33.0), MacOS: Version 10.13.6 I am running multiple, but CPU is 133 and spikes to 220 sometimes.... |
Small update: |
❗️ and everyone update to 1.33.1 first, there has been an issue with TS/JS which might have caused this |
Updated today, still experiencing the issue occuring. Here's the file you asked for: |
@lukasz-formela What is your list of installed extensions? ( |
As listed below:
A remark: I remember code being stuck with scss files at some point while opening big project. |
That sounds reasonable, the CPU profile point to S?CSS parsing and it will then be one your installed extensions (maybe scss-lint). There is nothing we can do here, except asking you file an issue against the extension. |
code helper seems to be consuming 100% of cpu with no extensions included. 😕 |
I am closing this as caused by extension because the only actionable provided information is from @lukasz-formela and the profile showed that this is an extension. Unfortunately, other me-too-comments without further information aren't actionable. |
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. Happy Coding! |
Issue Type: Performance Issue
From my research it can be something about "files.watcherExclude".
After running my VSCode instance ( many files in the folder that I open with it ) the fans start to roll out that 6k RPM and CPU goes to 100% usage.
VS Code version: Code 1.33.0 (0dd516d, 2019-04-04T15:11:32.076Z)
OS version: Darwin x64 18.5.0
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: unavailable_off
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Process Info
Workspace Info
Extensions (18)
(1 theme extensions excluded)
The text was updated successfully, but these errors were encountered: