Extension causes high cpu load
See original GitHub issue- Issue Type:
Performance
- Extension Name:
azure-pipelines
- Extension Version:
1.145.1
- OS Version:
Darwin x64 18.2.0
- VSCode version:
1.30.1
⚠️ Make sure to attach this file from your home-directory: /Users/daaronch/ms-azure-devops.azure-pipelines-unresponsive.cpuprofile.txt
⚠️
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 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 >Sfdx vs code Extension causes high cpu load
It's usually an extension acting up. In the command palette, run this to see all extensions and their startup time:
Read more >High CPU usage: What are the potential causes? - IONOS
Causes of high processor usage · Programs with higher CPU requirements: · Autostart programs: · Viruses · Browser: ...
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
ms-azure-devops.azure-pipelines-unresponsive.cpuprofile.txt
OK, sounds like the original issue is fixed. We don’t have any connection with “Pipelines” in that other extension, so I’ll close the issue.