microsoft / microsoft/vscode-cpptools
It takes way too long to finish tag parsing of modified files after a find/replace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
- Do a find/replace over many files.
- View the C/C++ logging for "tag parsing" messages.
Bug: It takes way too long to tag parse. Like each tag parse takes 1-2 seconds on Linux (seemed like 0.5-1 seconds on Windows), which is a lot slower than the speed of the initial tag parsing when a database is first created. From initial debugging it seemed like it could be some database update/lock issue.
But I don't think we've gotten a user complaint about this so I'm not sure how important it is to make this scenario faster.
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 find/replace scenario across many files and watch the C/C++ logging for "tag parsing" messages. Compare modified-file tag parsing with the initial database creation path, focusing on the reported database update or lock behavior. Done means the repeated tag parses complete substantially faster, especially on Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, linux
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100