Excessive CPU, Memory, and Energy Use When Salesforce Extension Pack is Enabled
See original GitHub issueSummary
When the Salesforce Extension Pack is enabled I am experiencing greatly increased CPU, memory, and energy use. Currently Visual Studio Code ‘Code Helper’ is using 214% CPU, 303 energy impact, and 1.86 GB memory.
Please let me know if there is any specific information I can supply.
Steps To Reproduce:
- Open a code base in Visual Studio Code with Salesforce Extension Pack enabled.
- Open Activity Monitor
- Note that Visual Studio Code Code Helper is using excessive resources.
Expected result
When using the Salesforce Extension Pack, Visual Studio Code consumes less resources and can be used on battery power.
Actual result
When using the Visual Studio Code Extension Pack, Visual Studio Code appears to use excessive resources and needs to be disabled in order to retain battery life.
Additional information
Feel free to attach a screenshot.
VS Code Version:
Version: 1.37.1
Commit: f06011ac164ae4dc8e753a3fe7f9549844d15e35
Date: 2019-08-15T16:16:34.800Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.7.0
SFDX CLI Version:
sfdx-cli/7.20.1-d88ae4707c darwin-x64 node-v10.15.3
OS and version:
macOS Mojave 10.14.6
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:14 (1 by maintainers)
Top Results From Across the Web
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 >Visual Studio Code 100%+ CPU Percentage - Salesforce ...
Visual Studio Code 100%+ CPU Percentage - Salesforce Extension is the culprit, fix? : r/salesforce.
Read more >Hottest Salesforce VS Code Extensions
If there's one set of extensions anyone working with VS Code and Salesforce needs, it is most definitely the Salesforce Extensions Pack.
Read more >Salesforce Extension Pack Review: Breakthrough Tool Needs ...
In this formal review of Salesforce Extension Pack for VS Code the product is graded on usability, customer service, and integration.
Read more >DocuSign for Salesforce Administrator Guide
Enable DocuSign Connect for Salesforce for use with the iPad ... The DocuSign® for Salesforce managed package allows users to send a ...
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
Here is a sample of the error output I get:
(node:2897) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [Error - 6:48:55 AM] (node:2897) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined at Object.indexStaticResources (/Users/caspar/.vscode/extensions/salesforce.salesforcedx-vscode-lightning-47.9.0/node_modules/lwc-language-server/lib/metadata-utils/static-resources-util.js:55:85) at async Promise.all (index 2) at async Promise.all (index 0) at async Timeout._onTimeout (/Users/caspar/.vscode/extensions/salesforce.salesforcedx-vscode-lightning-47.9.0/node_modules/aura-language-server/lib/server.js:39:9) [Error - 6:48:55 AM] (node:2897) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) [Error - 6:48:55 AM] (node:2897) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Hi guys, VSC today’s update fix the bug 😃