High cpu usage from unknown extension (likely NOT json) #232699
Assignees
Labels
bug
Issue identified by VS Code Team member as probable bug
candidate
Issue identified as probable candidate for fixing in the next release
extension-host
Extension host issues
freeze-slow-crash-leak
VS Code crashing, performance, freeze and memory leak issues
log
VS Code log issues
verified
Verification succeeded
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
Yes, I disabled this extension, but there is not any help. |
|
Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions. |
The problem is still having and be worse. |
|
It work well after downgrade to 1.94.2 |
|
Same issue on M1 Mac. |
|
Same issue on M1 Mac, fan is screaming. Bisect doesn't detect any issues.
Extension Host logEdit: Reverted to 1.94.2. No issue so far. Extension Host doesn't show any error messages |
|
@ddup93 Does disabling all extensions and restarting VS Code fix the issue for you? |
mjbvz
added
info-needed
|
VSCode version 1.95.1 Disable the extensions one by one and reload the vscode every time,and the result is not well. |
|
I have a guess that this is caused when different Profiles with the same Extensions are open and these using LSP through ipc-protocol. I disabled all these extensions and everything runs smoothly again.
|
I tried it and it didn't solve the problem; this issue has been bothering me for two days now; I am now using the cursor exclusively. |
Closed
|
Could you go through https://github.com/microsoft/vscode/wiki/performance-issues#visual-studio-code-is-consuming-a-lot-of-cpu to help track down the issue? |
|
@ddup93 and everyone, please do the following (assuming the EH process "Code Helper" consumes much CPU):
Screen.Recording.2024-11-01.at.11.51.25.mov |
|
@ddup93 Are you sure the extension host was running at high cpu during that? The profile shows just idle which suggests not, but there might be a problem outside of what we can capture with a CPU profile
|
sure. code helper (plugin) cpu is 96% |
|
@deepak1556 can you help? this seems to be "outside of v8" |
This comment has been minimized.
This comment has been minimized.
|
For me, |
|
You have to look in the process manager for these looking processes, hover over them, get the extension name and disable all on your side that are starting with /Application... |
Okay, Let me try, here's my extensions load when I disabled all extensions...
So when I disabled the first three extensions, I will still got 100% cpu for the |
|
Disabld json lang features you wont need them actually |
sandy081
added a commit
that referenced
this issue
Nov 13, 2024
sandy081
added a commit
that referenced
this issue
Nov 13, 2024
|
Can users confirm if the issue is addressed with latest insiders https://code.visualstudio.com/insiders, the fix will also be available with |
Just tried the insider version, looking good 👍 |
|
Insiders working good. It needs some time but it kills the old processes after some time. |
|
For me the old processes never kill, after some time i have 8 and my fans spinning crazy Which is even more awefull because i never used any AI integration and never will be. I didnt try the insider build yet but checking again when the update hits. |
|
Hey, @deepak1556 after the upgrade to 1.95.3 same issue is still appear on my intel based machine. I tried 1.96 and it works fine, no issues. Version: 1.95.3 (Universal) |
|
1.95.3 work well |
|
I too have still got this issue post upgrading to 1.95.3. |
|
My intel machine still has the issue on |
|
@Artofaj yes a targeted fix is in |
|
I posted a comment in this issue (apparently it is a dupe): After reading this thread that you're currently reading, it seems some are still experiencing this issue even in the latest insider build? If this is the case why has this issue been closed? Shouldn't more people confirm it is working first before merging and closing? |
|
@spacecat the fix we added in |
|
@deepak1556 thanks for the quick reply. I will keep my eyes open and let you know (with a cpu profile (if it's not too time consuming! 😁)) if I see the high CPU usage again. |
|
In my case, it's the file watcher under code main taking 100% CPU
|
|
Just observed this when I amend commit. Maybe related: 2024-11-21 17:38:30.452 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [26ms]
2024-11-21 17:38:30.504 [info] > git status -z -uall [81ms]
2024-11-21 17:38:46.649 [info] > git config --local branch.hover.merge [20ms]
2024-11-21 17:38:47.462 [info] > git -c user.useConfigOnly=true commit --quiet --amend [313ms]
2024-11-21 17:38:47.462 [info] Error: connect ENOENT /var/folders/lt/s79dbyyn5qngdf10r5jsx4k00000gp/T/vscode-git-9d7e8c4b06.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1607:16) {
errno: -2,
code: 'ENOENT',
syscall: 'connect',
address: '/var/folders/lt/s79dbyyn5qngdf10r5jsx4k00000gp/T/vscode-git-9d7e8c4b06.sock'
}
error: There was a problem with the editor '"/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/git-editor.sh"'.
Please supply the message using either -m or -F option. |
Hey @deepak1556 I tested how fix works in 1.96 and in my case issue still appears in Version: 1.96.0-insider |
|
VSCode's file handle usage is very high, which will cause the Mac to not work properly |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
Type: Performance Issue
high cpu usage
VS Code version: Code 1.95.0 (912bb68, 2024-10-28T20:16:24.561Z)
OS version: Darwin arm64 24.1.0
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Process Info
Workspace Info
Extensions (13)
The text was updated successfully, but these errors were encountered: