microsoft / microsoft/vscode-cpptools
Intellisense always updating
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: W11 Pro (10.0, compilation 22000)
- VS Code: 1.78 (The version doesn't matter. It happens with everyone)
- C/C++ extension: C/C++ Extension Pack v1.3.0 Microsoft
- GDB / LLDB version:
Bug Summary and Steps to Reproduce
Bug Summary:
Every time I save, the intellisense is activated again, indexing the entire project, making it impossible to perform its function, which is to display the methods, properties... as well as the information.
[ - Steps to reproduce the problem - ]
1 - I write the code
2 - When I save anything (right here the intellisense re-indexes the whole project)
Every time I save we get:
1 - Indexing of the entire project.
What it does is:
1 - When I save it sends a notify
2 - That notify indicates that it was saved or there was a change
3 - Index the entire project again.
Debugger Configurations
Is too long. I only put a part.
"version": "2.0.0",
"tasks": [
{
"label": "MyProject_test Win64 Debug Build",
"group": "build",
"command": "Engine\\Build\\BatchFiles\\Build.bat",
"args": [
"MyProject_test",
"Win64",
"Debug",
"E:\\IDE\\Epic Games\\Projects UE\\MyProject_test\\MyProject_test.uproject",
"-waitmutex"
],
"problemMatcher": "$msCompile",
"type": "shell",
"options": {
"cwd": "E:\\IDE\\UE_5.1"
}
},
{
Debugger Logs
-
Other Extensions
C/C++ Extension Pack (Microsoft)
- CMake Tools (Microsoft)
- CMake (Microsoft)
Additional Information
[Settings -> Intellisense]
C_Cpp: intelli Sense engine
Controls the Intellisense provider in
- "Tag Parser" (No) does not update compile-time errors
- Default (Yes) analyzes errors at compile time.
I can't put it in "Tag parser" otherwise it's like the errors don't work.
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 on Windows with the C/C++ extension, CMake Tools, and the Unreal Engine project described in the issue; save a file while observing IntelliSense indexing. Start with the IntelliSense settings and save/notify behavior, then compare the full-project indexing activity before and after a save. Done means normal saves no longer trigger unnecessary full-project reindexing while compile-time errors remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, typescript, unreal-engine, vscode
- Domain
- developer-experience, performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100