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.
VSCode’s renderer helper process using 100% of CPU
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes/No
- VS Code Version:1.66.2
- OS Version: Darwin arm64 21.4.0
提交: dfd34e8260c270da74b5c2d86d61aee4b6d56977 日期: 2022-04-11T07:47:29.396Z Electron: 17.2.0 Chromium: 98.0.4758.109 Node.js: 16.13.0 V8: 9.8.177.11-electron.0
The vscode Code Helper (Renderer) process consumes a lot of cpu and causes a very high processor temperature, closing vscode and disabling all extensions will not solve the problem. After a clean reinstall the problem persisted. The way to reproduce is to open vscode and use the search function will appear, and vscode’s own process manager does not show this abnormal process, you need to manually go to apple’s process manager to end the task.
Issue Analytics
- State:
- Created a year ago
- Reactions:26
- Comments:48 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I confirmed that the settings-sync extension was causing the problem, and it was resolved by turning off the extension.
same problem here. In my case, disabled code-settings-sync extension solved the problem.