Extension causes high cpu load
See original GitHub issue- Issue Type: 
Performance - Extension Name: 
terraform - Extension Version: 
2.1.1 - OS Version: 
Darwin x64 17.7.0 - VSCode version: 
1.48.0 
⚠️ Make sure to attach this file from your home-directory:
⚠️/Users/yosef_bw/hashicorp.terraform-unresponsive.cpuprofile.txt
hashicorp.terraform-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
Issue Analytics
- State:
 - Created 3 years ago
 - Comments:6 (3 by maintainers)
 
Top Results From Across the Web
Extension causes high cpu load · Issue #2983 - GitHub
I'm not able to repro high CPU utilization when opening or modifying the files you mentioned. From your logs, I see a couple...
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 Free
Top 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

I’m going to close this issue for now as I wasn’t able to reproduce it, but do let us know if it occurs again.
I’m going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.