Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Extension causes high cpu load

See original GitHub issue

Issue Type: Performance
Extension Name: aws-toolkit-vscode
Extension Version: 1.39.0
OS Version: Windows_NT x64 10.0.19043
VS Code version: 1.68.1

⚠️ Make sure to attach this file from your home-directory: ⚠️file:///c%3A/Users/super/AppData/Local/Temp/amazonwebservices.aws-toolkit-vscode-unresponsive.cpuprofile.txt

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

Issue Analytics

State:
Created a year ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

sdee3commented, Aug 2, 2022

@sdee3 can you reproduce the issue after uninstalling/disabling ALL extensions except AWS Toolkit and whatever debugger is needed for debugging your Lambda?

I tried this, and I also isolated the extension via extensions.experimental.affinity. I got a really good result:

Reverting all other extensions quickly got me back to the same usage patterns, after which I decided to open the Running Extensions window and Profile all of them while debugging my Lambda. This led me to a conclusion that wix.vscode-import-cost is the culprit, using over 99% of all resources to investigate a bundled JS file I use for debugging, and after disabling only that extension, my CPU is behaving normally. @justinmk3 thank you for suggesting where to look and your support!

1reaction

justinmk3commented, Aug 1, 2022

possibly related to file watchers,

potentially useful: vscode now has extensions.experimental.affinity which can isolate extensions to their own process.