microsoft / microsoft/vscode-cpptools
Opening many editors cripples my machine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Windows_NT x64 10.0.19043
- VS Code Version: 1.70.2
- C/C++ Extension Version: 1.11.5
Bug Summary and Steps to Reproduce
Bug Summary:
When opening many editors the extension spins up so many Intellisense processes my PC becomes unresponsive and unusable until I kill them manually or close VSCode. These processes linger even after closing editors.
Steps to reproduce:
- Open many editors (10-30)
- Notice the number of Intellisense processes running in the background and the resulting CPU usage
- Close all editors
- Notice the Intellisense processes stick around for a long time (possibly until they finish?)
For additional context, this happens in an Unreal Engine codebase (where includes are notoriously heavy and Intellisense has its work cut out for it) while making sweeping refactoring changes. I end up opening 10-20 files at a time, making the same change to each of them, then closing them and starting another batch.
Expected behavior
- The number of Intellisense processes for unfocused editors is limited to a reasonable number based on the available CPU cores.
- Intellisense processes are closed immediately when an editor is closed.
Code sample and Logs
.
Screenshots
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the reported Windows, VS Code, and C/C++ extension versions with 10–30 editors in an Unreal Engine codebase. Trace how IntelliSense processes are created for unfocused editors and what happens when editors close. Done means unfocused work is reasonably limited by available CPU cores and processes exit promptly after editors are closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100