Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Helper (Renderer) uses 100% of CPU in background with ESLint plugin #239173

Closed
kool79 opened this issue Jan 30, 2025 · 3 comments
Closed

Code Helper (Renderer) uses 100% of CPU in background with ESLint plugin #239173

kool79 opened this issue Jan 30, 2025 · 3 comments
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@kool79
Copy link

kool79 commented Jan 30, 2025

Does this issue occur when all extensions are disabled?: Yes/No
Dont know. But in my case I have a fresh Mac, VSCode and 2 extensions only -- ESLint and GitHub Copilot.

  • VS Code Version: 1.96.3
  • OS Version: Sonoma 14.6.1 @ M2Max

Steps to Reproduce:

  1. Install ESLint
  2. Open any VSCode project (with react native in my case)
  3. Dont touch anything else during some period of time
  4. look into Activity Monitor.
    There are 2 processes with a name "Code Helper (Renderer)", every process shows ~300..400% CPU. When close VSCode, processes are not terminated.

I think that it is a duplicate for #101555, but that issue was created ~5years ago and no movement since then. This bug just eats my battery -- Actually the energy saving was the main reason why I bought my mac. And VSCode just wastes the energy and "helps" to destroy oxygen on the Earth

Copy link

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.96.4. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

@kool79 kool79 changed the title Code Helper (Renderer) uses 100% of CPU in backgroun with ESLint plugin Code Helper (Renderer) uses 100% of CPU in background with ESLint plugin Jan 30, 2025
@gjsjohnmurray
Copy link
Contributor

/causedByExtension

Thanks for reporting this on the extension's repo where it initially belongs.

@vs-code-engineering vs-code-engineering bot added the *caused-by-extension Issue identified to be caused by an extension label Jan 30, 2025
Copy link

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants