Why is Visual Studio Code using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Visual Studio Code is an Electron app: each window runs in a Code Helper (Renderer) process, and extensions run in an extension host that appears as Code Helper (Plugin). High CPU almost always comes from an extension, a language server, or searching and watching a folder with a very large number of files. Help > Open Process Explorer shows which part is busy, and Help: Start Extension Bisect finds a misbehaving extension.
What are the Code Helper processes?
VS Code 1.138 for Mac contains Electron Framework and four helper apps. In Activity Monitor they appear as:
- Code: the main process that manages windows and updates.
- Code Helper (Renderer): one per window, drawing the editor and its panels.
- Code Helper (Plugin): the extension host and other Node-based workers, including language servers started by extensions.
- Code Helper (GPU): drawing with the graphics processor.
- Code Helper: utility processes such as the file watcher and the shared process.
Language servers and tools that extensions start can also appear under their own names, such as node, python3 or java.
How do you find what is making VS Code busy?
- Open Process Explorer. Choose Help > Open Process Explorer. It lists VS Code's processes with CPU and memory and keeps updating.
code --statusin Terminal prints the same information. - Start without extensions. Run
code --disable-extensionsfrom Terminal. If the CPU use disappears, an extension is the cause. - Bisect your extensions. Open the Command Palette (Shift-Command-P) and run Help: Start Extension Bisect. VS Code disables half your extensions at a time and asks whether the problem is still there until one remains.
- See what extensions are doing. Run Developer: Show Running Extensions to see each extension's activation time, and record a CPU profile of the extension host from that view.
- Exclude huge folders. If VS Code becomes unresponsive after opening a folder with very many files, exclude generated or vendored folders with the
files.excludesetting.
Why does VS Code's memory keep growing?
Each open window is a renderer, and each language extension may run a language server that holds an index of your project in memory. TypeScript, Java, C++ and Python servers can each use a large share of memory on a big codebase. Closing windows you are not using, and disabling language extensions for languages you do not work in, reduces the total.
The VS Code FAQ also notes that when AI features are disabled, no background processes associated with them run.
When should VS Code's resource use concern you?
A Code Helper (Plugin) row that stays at high CPU while you are not typing is the most common sign of a problem, and Process Explorer will show the extension host or a child process as the source. A Code Helper (Renderer) at high CPU points to the editor itself, often a very large file open with syntax highlighting. Report reproducible cases with the CPU profile from Show Running Extensions.
How can Thrum help with Visual Studio Code?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Visual Studio Code is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Visual Studio Code in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
Which extension is slowing VS Code down?
Run Help: Start Extension Bisect from the Command Palette. It narrows the problem down to one extension in a few restarts.
Why is Code Helper (Plugin) using 100% CPU?
That process hosts extensions. One extension, or a language server it started, is doing continuous work. Process Explorer and Show Running Extensions identify it.
Sources
- VS Code wiki: Performance Issues
- VS Code documentation: FAQ
- Helper apps listed in Visual Studio Code 1.138.0 for Mac