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

Extension causes high cpu load #841

Closed
st-schneider opened this issue Jan 28, 2019 · 14 comments
Closed

Extension causes high cpu load #841

st-schneider opened this issue Jan 28, 2019 · 14 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug performance verified Verification succeeded

Comments

@st-schneider
Copy link

st-schneider commented Jan 28, 2019

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@paustint
Copy link

I have been having problems with this as well and I was able to capture a CPU profile while I had 100% CPU from this extension. I was not even using the extension at all, so it was running in the background and looks like it was stuck in garbage collection. The profile was for about 10-20 seconds.

CPU-20200318T155400.148Z.cpuprofile.txt

@brianminsk
Copy link

brianminsk commented Jun 17, 2020

Same issue. I've attached the automatically generated profile.
VSCode version: 1.46.0

GitHub.vscode-pull-request-github-unresponsive.cpuprofile.txt

@killshot13
Copy link

Ditto ☝️.
Observed right after installing the latest version of VS Code.

Version: 1.61.1 (system setup)
Commit: c13f1abb110fc756f9b3a6f16670df9cd9d4cf63
Date: 2021-10-14T01:19:42.089Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

GitHub.vscode-pull-request-github-unresponsive.cpuprofile

@ghost
Copy link

ghost commented Nov 30, 2021

Same here on Windows 10

Version: 1.62.3 (system setup)
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:11:14.551Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044

GitHub.vscode-pull-request-github-unresponsive.cpuprofile.txt

@amigowifigh
Copy link

awgh

@alexr00 alexr00 added this to the December 2021 milestone Dec 7, 2021
@alexr00 alexr00 self-assigned this Dec 7, 2021
@transcental
Copy link

Same issue here on macOS:

System details

Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:37:28.172Z (4 days ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 19.6.0 - macOS Catalina 10.15.7

Gist - https://gist.github.com/DillonB07/5ae1a3259f1d789d08469f33db39be93

@alexr00
Copy link
Member

alexr00 commented Dec 21, 2021

I've started looking through several of the profiles in this issue (thanks everyone who added one!). The high CPU seems to occur when several extensions are activating at once. ritwickdey.liveserver in particular seems to coincide with the high CPU, so folks who have that installed might try disabling it.

Is everyone seeing this high CPU associated with GitHub Pull Requests and issues shortly after starting or reloading VS Code?

@alexr00 alexr00 removed this from the January 2022 milestone Dec 21, 2021
@alexr00 alexr00 added the info-needed Issue requires more information from poster label Dec 21, 2021
@transcental
Copy link

Yes. I do have the liveserver extension installed but I'll try disabling that and see how it works.

I am seeing the issue after starting/reloading VSC though.

@transcental
Copy link

However, disabling the liveserver extension didn't seem to help.

CPU Log - https://gist.github.com/DillonB07/72bef869458babec53e19efd0127373b

@alexr00
Copy link
Member

alexr00 commented Dec 27, 2021

Thanks for trying that @DillonB07 and for the new profile. After further digging, it looks like one of the modules we include may be slow (https://www.npmjs.com/package/vscode-extension-telemetry). I'm following up with the owners to see if that's the case and if it can be improved.

@alexr00 alexr00 removed the info-needed Issue requires more information from poster label Dec 27, 2021
@alexr00 alexr00 added this to the January 2022 milestone Dec 27, 2021
@alexr00
Copy link
Member

alexr00 commented Dec 27, 2021

Module has been updated, and I've pulled the update in to this extension.

The pre-release build will have the fix tomorrow (the version number will be 0.35.20211228*). If folks in this thread could try it out after that build is ready tomorrow and comment your results it would help confirm whether we've tracked the perf issue down or if the issue should be reopened for further investigation.

@alexr00
Copy link
Member

alexr00 commented Dec 27, 2021

Once I get confirmation that the perf issue is fixed from someone in this thread, I'll release 0.34.3 with the change!

@transcental
Copy link

I haven't got the issue anymore. Seems like it's fixed.

Thanks!

@alexr00
Copy link
Member

alexr00 commented Jan 3, 2022

Thanks @DillonB07, I'll release 0.34.3 with the fix.

@alexr00 alexr00 removed this from the January 2022 milestone Jan 6, 2022
@alexr00 alexr00 added bug Issue identified by VS Code Team member as probable bug verified Verification succeeded labels Jan 6, 2022
@alexr00 alexr00 added this to the November 2021 Recovery 3 milestone Jan 6, 2022
alexr00 added a commit that referenced this issue Jan 6, 2022
This was referenced Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug performance verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

8 participants