Skip to content
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

Closed
lukasz-formela opened this issue Apr 9, 2019 · 22 comments
Closed

100%+ CPU usage from "Code Helper". #72002

lukasz-formela opened this issue Apr 9, 2019 · 22 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension info-needed Issue requires more information from poster

Comments

@lukasz-formela
Copy link

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
Item Value
CPUs Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz (8 x 2600)
GPU Status 2d_canvas: enabled
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
Load (avg) 2, 2, 2
Memory (System) 16.00GB (2.66GB free)
Process Argv -psn_0_65552
Screen Reader no
VM 0%
Process Info
CPU %	Mem MB	   PID	Process
   18	    98	   284	code main
    0	    98	   390	   gpu-process
    0	    98	   423	   shared-process
    0	   377	  1132	   window (Settings — Projects)
    0	     0	  1133	     /bin/bash -l
    0	    66	  1137	     watcherService
    0	    98	  1411	   window (Issue Reporter)
    0	     0	  1413	   /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
Workspace Info
|  Window (Settings — Projects)
|    Folder (Projects): more than 25639 files
|      File types: php(11366) png(5538) js(1741) scss(1128) css(894) svg(526)
|                  md(434) gif(414) eps(340) json(321)
|      Conf files: gulp.js(27) makefile(9) settings.json(1) package.json(1);
Extensions (18)
Extension Author (truncated) Version
scss-lint ada 0.1.8
conflict-squeezer ang 1.0.1
vagrant bbe 0.5.0
vscode-tailwindcss bra 0.1.16
gitlens eam 9.6.0
vscode-html-css ecm 0.2.0
auto-close-tag for 0.5.6
html-slim-scss-css-class-completion gen 1.5.14
beautify Hoo 1.4.11
githd hui 2.1.0
html-tag-wrapper hwe 0.2.3
composer ika 0.7.1
code-beautifier mic 2.2.1
live-sass rit 3.0.0
LiveServer rit 5.5.1
laravel-artisan rya 0.0.25
git-merger sha 0.4.1
highlight-matching-tag vin 0.9.1

(1 theme extensions excluded)

@TotesOates
Copy link

TotesOates commented Apr 9, 2019

Try rm -r ~/Library/Caches/TypeScript/3.4 and restarting VS code

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

@lukasz-formela
Copy link
Author

Zrzut ekranu 2019-04-9 o 17 40 00

Was worth a shot but sadly didn't help.
In two minutes after opening VS code it goes to 4th density mode.

@lukasz-formela
Copy link
Author

#3998 (comment)

I added the suggested temp folder but still there's no change.
**/tmp/**

@steveoon
Copy link

steveoon commented Apr 10, 2019

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.

@soorajvnair
Copy link

Yes. Same here. Switched to an insiders build, works fine.

@bpasero bpasero assigned jrieken and alexdima and unassigned bpasero Apr 10, 2019
@bpasero
Copy link
Member

bpasero commented Apr 10, 2019

image

@lukasz-formela
Copy link
Author

lukasz-formela commented Apr 10, 2019 via email

@jrieken
Copy link
Member

jrieken commented Apr 10, 2019

Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions. Thanks.

@jrieken jrieken added the info-needed Issue requires more information from poster label Apr 10, 2019
@gi
Copy link

gi commented Apr 10, 2019

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.

@lukasz-formela
Copy link
Author

Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions. Thanks.

What if:
[Public-:~ $ code --inspect-extensions=9993
-bash: code: command not found] ?

@ddzy
Copy link

ddzy commented Apr 13, 2019

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
Process Info
Workspace Info
Extensions (18)

Same issue(#67150)

@Chazie9
Copy link

Chazie9 commented Apr 15, 2019

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

@jrieken
Copy link
Member

jrieken commented Apr 15, 2019

@lukasz-formela
Copy link
Author

Small update:
Overheating starts when 'Initializing JS/TS language features'.
I'll try to follow @jrieken instructions.

@jrieken
Copy link
Member

jrieken commented Apr 15, 2019

❗️ and everyone update to 1.33.1 first, there has been an issue with TS/JS which might have caused this

@lukasz-formela
Copy link
Author

❗️ 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:
CPU-20190415T081025.506Z.cpuprofile.txt

@jrieken
Copy link
Member

jrieken commented Apr 15, 2019

@lukasz-formela What is your list of installed extensions? (code --list-extensions)

@lukasz-formela
Copy link
Author

lukasz-formela commented Apr 15, 2019

As listed below:

adamwalzer.scss-lint
akamud.vscode-theme-onedark
angelomollame.conflict-squeezer
bbenoist.vagrant
bradlc.vscode-tailwindcss
eamodio.gitlens
ecmel.vscode-html-css
formulahendry.auto-close-tag
gencer.html-slim-scss-css-class-completion
HookyQR.beautify
huizhou.githd
humao.rest-client
hwencc.html-tag-wrapper
ikappas.composer
michelemelluso.code-beautifier
octref.vetur
oderwat.indent-rainbow
ritwickdey.live-sass
ritwickdey.LiveServer
ryannaddy.laravel-artisan
shaharkazaz.git-merger
vincaslt.highlight-matching-tag

A remark: I remember code being stuck with scss files at some point while opening big project.

@jrieken
Copy link
Member

jrieken commented Apr 15, 2019

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.

@GeorgiosP
Copy link

GeorgiosP commented Apr 17, 2019

code helper seems to be consuming 100% of cpu with no extensions included. 😕

@jrieken
Copy link
Member

jrieken commented Apr 17, 2019

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.

@jrieken jrieken added the *caused-by-extension Issue identified to be caused by an extension label Apr 17, 2019
@vscodebot
Copy link

vscodebot bot commented Apr 17, 2019

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!

@vscodebot vscodebot bot closed this as completed Apr 17, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests