Symptoms & Diagnosis
Is your cooling fan spinning at maximum speed while you are simply editing text? VS Code high CPU usage can manifest as input lag, delayed intellisense, or a total system freeze.
To diagnose the root cause, use the internal Process Explorer. You can open this by navigating to Help > Open Process Explorer or by pressing Shift + Escape. This tool shows exactly which child process—be it the renderer, an extension host, or a language server—is consuming your cycles.
Common culprits often include recursive file watching in large directories, outdated extensions, or incompatible hardware acceleration settings.
Troubleshooting Guide
Follow these systematic steps to lower the CPU load and regain a smooth coding experience.
1. Isolate Rogue Extensions
The Extension Host is a frequent source of performance leaks. To verify if an extension is at fault, launch VS Code from your terminal with all plugins disabled:
code --disable-extensionsIf the CPU usage stabilizes, re-enable your extensions one by one to find the specific plugin causing the spike.
2. Disable Hardware Acceleration
On certain hardware configurations, Electron’s GPU acceleration can conflict with drivers. You can test this by launching the editor with the following flag:
code --disable-hardware-accelerationIf this resolves the issue, you can make it permanent by editing your argv.json file (accessible via the Command Palette).
3. Optimize File Watcher Settings
VS Code continuously monitors your project for changes. If you are working in a massive repository (like those containing node_modules), the watcher may become overwhelmed.
Update your settings to exclude heavy directories:
| Setting Key | Recommended Exclusion Pattern |
|---|---|
| files.watcherExclude | “**/node_modules/*/**”: true |
| files.exclude | “**/.git”: true |
| search.exclude | “**/dist/**”: true |
4. Clear the Editor Cache
Sometimes corrupted cache files lead to persistent CPU spikes. Close VS Code and delete the “Code” folder in your application data directory to reset the environment state.
Prevention
To prevent future performance degradation, keep your editor and extensions updated. Microsoft frequently releases patches that address memory leaks and CPU optimization.
Adopt a “minimalist extension” policy. Disable language-specific extensions when you are not working in that specific environment using the “Disable (Workspace)” feature.
Finally, ensure your project’s .gitignore is properly configured, as VS Code uses these rules to help decide which files to ignore during background indexing tasks.