microsoft / microsoft/vscode-cpptools
Slow and unstable on bigger workspaces
Open
Nobody has claimed this yet.
bug
investigate: repro
Language Service
performance
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Linux ANY
- VS Code Version: ANY
- C/C++ Extension Version: ANY
- If using SSH remote, specify OS of remote machine: LINUX
Bug Summary and Steps to Reproduce
My workspace contains an equivalent of ~ 3 llvm trunks.
- Too slow in scanning workspace.
- May stop working: sometimes it finds definition (after window reload), sometimes it doesn't.
- Symbols lookup is not working in my workspace: results in "C++ server disconnected" every time.
- Outline display is too slow and sometimes works only after "reload Intellisence for active file"
I've set all the settings, raized cache sizes, etc, still it's unreliable. Better than nothing, still far from perfect.
Please make it workable and more stable for large workspaces.
Configuration and Logs
-
Other Extensions
NO
Additional context
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
Reproduce the problems with scanning, definition lookup, symbol lookup, and outline display in a workspace equivalent to about three LLVM trunks. Compare behavior before and after window reload or reloading IntelliSense; done means large workspaces remain responsive and these features work reliably without the C++ server disconnecting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100