microsoft / microsoft/vscode-cpptools
Unnecessary duplicate "Processing folder" calls may be run with multiple root folders
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
With the new multi-root implementation (0.27.0-insiders3 or later), if you see a lot of duplicate "Processing folder" in the logging and CPU is being used then it's this issue (it's common with system header paths that are shared across workspace folders). It's somewhat "by design" because every folder could have different settings (e.g. files.exclude, limitSymbolsToIncludedHeaders, etc.), so we don't know currently which "Processing folders" are unnecessary (without adding additional code).
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 multi-root case described in the issue, watching for duplicate "Processing folder" log entries and CPU use when system header paths are shared across workspace folders. Trace the folder-processing entry point and the per-folder settings such as files.exclude and limitSymbolsToIncludedHeaders; done means unnecessary duplicate work is avoided without changing behavior for folders with different settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100