cpptools takes hours of CPU time per day for a project which compiles in 5 seconds
**Type: LanguageService** **Describe the bug** - OS and Version: OSX 10.15.4 - VS Code Version: 1.45.1 - C/C++ Extension Version: 0.28.1 For every C++ project, even tiny ones which compile in a few seconds, a cpptools process runs for something between 6 and 40 minutes every time I open the project and also from time to time after editing or git operations. Over the day this accumulates to many hours and estimated about 25% of the time my laptop fan runs cause of cpptools (it hardly every runs cause of compiles). Also the memory consumption of cpptools is fairly high - around 7GB is common. I guess this has to do with scanning system headers, but is still seems wasteful to spend 30 minutes on symbol analysis for a project where a release build takes 5 seconds. This is not really a bug, but to me it looks like unnecessary waste of resources. One more observation: when I delete the folder in which VSCode keeps the database (on Mac `~/Library/Application Support/VSCodium/User/workspaceStorage/`) it runs the first time "only" for 6 minutes - Intellisense is fully operational. The second time it decides to run for the same projects - about 1 hour later - it runs for 29 minutes. **Steps to reproduce** - Open any project with C files - Look at the CPU time of the cpptools process **Expected behavior** - cpptools needs less than 10x the compile time In case you cannot reproduce this (for me this happens for every C++ project every time since at least 6 months) I can of cause pr
Posted by MSoegtropIMC on May 27, 2020, 9:29 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
cpptools takes hours of CPU time per day for a project which compiles in 5 seconds
**Type: LanguageService** **Describe the bug** - OS and Version: OSX 10.15.4 - VS Code Version: 1.45.1 - C/C++ Extension Version: 0.28.1 For every C++ project, even tiny ones which compile in a few seconds, a cpptools process runs for something between 6 and 40 minutes every time I open the project and also from time to time after editing or git operations. Over the day this accumulates to many hours and estimated about 25% of the time my laptop fan runs cause of cpptools (it hardly every runs cause of compiles). Also the memory consumption of cpptools is fairly high - around 7GB is common. I guess this has to do with scanning system headers, but is still seems wasteful to spend 30 minutes on symbol analysis for a project where a release build takes 5 seconds. This is not really a bug, but to me it looks like unnecessary waste of resources. One more observation: when I delete the folder in which VSCode keeps the database (on Mac `~/Library/Application Support/VSCodium/User/workspaceStorage/`) it runs the first time "only" for 6 minutes - Intellisense is fully operational. The second time it decides to run for the same projects - about 1 hour later - it runs for 29 minutes. **Steps to reproduce** - Open any project with C files - Look at the CPU time of the cpptools process **Expected behavior** - cpptools needs less than 10x the compile time In case you cannot reproduce this (for me this happens for every C++ project every time since at least 6 months) I can of cause pr
Comments (0)
No comments yet. Start the discussion.