microsoft / microsoft/vscode-cpptools
IntelliSense gets stuck on Parsing workspace files, usually between 20% to 40%.
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
Environment
- OS and Version: Windows 11 [10.0.22631.4317]
- VS Code Version: 1.94.0, 1.94.2 (tested both)
- C/C++ Extension Version: 1.21.6
Bug Summary and Steps to Reproduce
Bug Summary:
I created a simple project to try the Tracy profiler (https://github.com/wolfpld/tracy).
- Tracy added as a submodule
- Created a Makefile with one target and two source files:
main.cppandTracyProfiler.cpp - The compiler is MSVC, and VSCode is launched through the Developer Command Prompt for VS 2022
- The Makefile Tools extension is used as the configuration provider, but disabling it makes no noticeable difference
Steps to Reproduce:
- Start VSCode and open my workspace
- IntelliSense begins parsing, and I can see it becoming active as I follow the paths
- It gets stuck halfway through (or earlier; it's random) and becomes unresponsive
My project files (without tracy repo)
tracy-test.zip
Full logs
logs.zip
Expected Behavior:
IntelliSense should successfully finish parsing and continue working as expected.
Configuration and Logs
-------- Diagnostics - 10/10/2024, 9:54:32 PM
Version: 1.21.6
Current Configuration:
{
"name": "Win32",
"includePath": [
"c:/Developement/tracy-test/",
"c:/Developement/tracy-test/tracy/public/tracy/"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.19041.0",
"compilerPath": "cl.exe",
"cStandard": "c17",
"cppStandard": "c++17",
"compilerPathInCppPropertiesJson": "cl.exe",
"intelliSenseMode": "msvc-x64",
"intelliSenseModeIsExplicit": true,
"cStandardIsExplicit": false,
"cppStandardIsExplicit": false,
"mergeConfigurations": true,
"compilerPathIsExplicit": false,
"configurationProvider": "ms-vscode.makefile-tools",
"browse": {
"path": [
"c:/Developement/tracy-test/",
"c:/Developement/tracy-test/tracy/public/tracy/",
"${workspaceFolder}"
],
"limitSymbolsToIncludedHeaders": true
}
}
cpptools version (native): 1.21.6.0
Translation Unit Mappings:
[ C:\Developement\tracy-test\main.cpp - source TU]:
Translation Unit Configurations:
[ C:\Developement\tracy-test\main.cpp ]:
Process ID: 10752
Memory Usage: 167 MB
Compiler Path: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64\cl.exe
Includes:
C:\Developement\tracy-test
C:\Developement\tracy-test\tracy\public\tracy
System Includes:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.31.31103\include
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.31.31103\atlmfc\include
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\cppwinrt
Defines:
TRACY_ENABLE
_DEBUG
UNICODE
_UNICODE
Standard Version: ms_c++17
IntelliSense Mode: windows-msvc-x64
Total Memory Usage: 167 MB
------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 5293
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia riproducendo il blocco durante l’analisi del workspace con il progetto allegato tracy-test.zip ed esamina l’allegato logs.zip, usando la configurazione e la diagnostica riportate come riferimento. Il lavoro è completato quando IntelliSense termina l’analisi invece di non rispondere più tra circa il 20% e il 40%.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- Ambito
- tooling
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100