Extension causes high cpu load
See original GitHub issue- Issue Type:
Performance
- Extension Name:
vscode-wakatime
- Extension Version:
4.0.0
- OS Version:
Windows_NT x64 10.0.18363
- VSCode version:
1.43.0
⚠️ Make sure to attach this file from your home-directory:
⚠️C:\Users\RaymundoDG\WakaTime.vscode-wakatime-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Extension causes high cpu load · Issue #1033 - GitHub
Recently I upgraded my global eslint to v7, if that's important, but I believe the high CPU usage goes back a long way....
Read more >[SOLVED] Chrome High CPU Usage - Driver Easy
Chrome extensions are also known to cause Chrome high system resources usage, such as 100% CPU, memory or disk usage.
Read more >VS Code using all of the CPUs and how to fix it - Remy Sharp
TL;DR: (yes, I ramble): use "Start extension bisect" in VS Code, it'll take less than 5 minutes. This is what I'm talking about....
Read more >High CPU usage: What are the potential causes? - IONOS
CPU usage indicates the degree of processing power that a PC's running processes require at any given moment. If it is too high,...
Read more >High CPU usage due to CEPHtmlEngine - Adobe Support
Solution 1: Delete the plug-in extension folder causing high CPU usage · Solution 2: Check the log files folder · macOS · Windows...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Probably fixed in v7.0.0 of the vscode extension, now that we’re using the new wakatime-cli that removes the Python dependency.
Also happening to me with almost zero reproducibility. Some days it will happen every hour, other times I won’t see it for days. Will be trying the suggestion above to see if it helps.