microsoft / microsoft/vscode-cpptools
workspace config dir continuously being polled
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: Debian 12
- VS Code Version: 1.85.1
- C/C++ Extension Version: 1.18.5
Bug Summary and Steps to Reproduce
Bug Summary:
Extension seems to cause continuous polling of the workspace config directory (.vscode/ on Linux)
Steps to reproduce:
- Have extension enabled
- run
sudo strace -f -t -e trace=file -p <vscode_pid> - see disk access
Expected behavior:
To not have extraneous access to this directory.
Configuration and Logs
After doing an extension troubleshoot from the vscode help (bisecting the loaded extensions) this extension ended up being the culprit of the extensive disk access.
For now I have this extension completely disabled.
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 issue with the C/C++ extension enabled by tracing the VS Code process with strace -f -t -e trace=file and observing access to the workspace .vscode/ directory. Compare this with the extension disabled or after extension bisecting; done means the extension no longer causes continuous extraneous polling of that directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100