file outline slow

[amigo421]

I've opened the project as folder , all required paths added to includePath.

when I open some file ~500 lines, Loading document symbols for ... takes an hours!!

"Tag parser initializing.." also for an hours and nothing more happens.
so no any symbol can be resolved

last version of VS from stable branch (auto-updated)
remote linux mode WIn10=>RHEL7

also I see this in the log: IntelliSense client not available, using Tag Parser for go to definition

[sean-mcmanus]

If you don't open a file and instead run C/C++: Rescan Workspace does it still take a long time for the database status icon to disappear? Or if you open a file with just "int main() { return 0; }"?

Are you using WSL1 or WSL2 and are you files resident on in the WSL VM or on the Windows /mnt/?

[amigo421]

thank you , I'll try this technique as well

but for now , could you clarify me please,
when I call workspace rescan , all folders included into this will be rescaned, right?

probably you remember , I was asking you some time ago about how to add search the files and symbols in Ctrl+P/O , and the adding all "includes" into the workspace was recommended .

so now , some include folders exist as "includePath" as well as added into the workspace for the navigation.

looks like double parsing? probably this is a root of the issue.

by the way, SSH FS extension adds remote file systems into the my workspace, is it also in parsing procedure?

[sean-mcmanus]

It should rescan all the folders included in the browse.path setting (which by default includes folders from includePath and from querying the compilerPath as well) but excluding files.exclude paths.

We have logic that should avoid double scanning. Your logging should show messages like "Processing folder" that shows what folders are being processed.

All processing is done on the remote machine.

[amigo421]

could you explain please what does "Configuration for file ... was not found" mean?
a number of such messages in C++ log...

[amigo421]

after the removing all external paths it parses the files but still veeeery slowly some files requires a min, some ones -10 mins,
but the problem is not this for the moment.
unfortunately it parses wrongly.
even basic parse by classes and methods is incorrect. "outline" of the file doesn't reflect real structure.
e.g. it doesn't see one method in the class but "think" that macro is a method (really - macro is inside the method and expands into range loop)

[sean-mcmanus]

"Configuration for file...was not found" can occur if you have compileCommands or configurationProvider set but open a file that doesn't have configuration info from those sources.

I'm not sure what could be causing the slow parsing...is the remote machine slow? Are the slow parses on small or large files?

The incorrect parsing sounds like it could be caused by defines that break our parser. Any defines that need to evaluated in order to parse correctly need to be added to a cpp.hint file (https://docs.microsoft.com/en-us/cpp/build/reference/hint-files?view=msvc-160).