Go to Symbol in File... is extraordinarily slow.

[Zooce]

I'm coming from Sublime Text, so maybe I'm a bit spoiled in this regard, but one of the main features I use in Sublime Text is searching for symbols. VS Code has this feature, but for some reason it takes an extremely long time for any symbols to be found in my project. The project is massive, and some files can be quite large themselves, however this happens even with small files (e.g. < 400 lines) and seems like it should be a pretty standard procedure no matter the project size.

• VSCode Version: 1.19.2
• OS Version: Windows 7 x64
• C/C++ Extension Version: 0.14.6

Steps to Reproduce:

1. Open a .cpp file with function definitions inside (obviously don't open a blank .cpp file)
2. Go > Go to Symbol in File...
3. If it is the first time running this, no symbols will be found (esc. and try step 2 again)
4. Wait for symbols to be parsed - it will sit there searching for a long time

[sean-mcmanus]

I'm able to repro the issue. This problem has existed "forever". Our symbol search engine appears to be iterating over all symbols in the entire database, so the operation is linear in the size of your browse.path so most of the time it is just hitting symbols in different files. It's faster the 2nd time because it cashes the results.

[Zooce]

So, the search doesn't understand the "in File..." part of "Go to Symbol." Thank you for looking into this, @sean-mcmanus.

[sean-mcmanus]

We were actually computing the search results quickly for the specific file, but afterwards a 2nd workspace cache building operation was being done unnecessarily, blocking the results.

The search results (and all other operations) can still be blocked by the red flame if your translation unit takes too long to parse, but that's a different issue.

[sean-mcmanus]

Fixed with the preview .vsix at https://github.com/Microsoft/vscode-cpptools/releases/tag/v0.15.0-insiders (our final release is planned for next week). Go to Symbol in Workspace can still be slow the 1st time due to the symbol cache generation and if you do a Go to Symbol in Workspace right before a Go to Symbol in File, it can block the "in File" results, because they're sent to the same processing queue.

[Zooce]

Thanks, @sean-mcmanus! So far it's working like a charm. I really appreciate it.

[ababak]

It's still extremely slow on Linux Version 1.24.1 + Python 2018.5.0 (05 Jun 2018)

[sean-mcmanus]

@ababak Can you provide more repro info in a new bug? Go to Symbol in File should be really fast unless it's blocked by another operation (e.g. testing with Chromium on Linux). Is there a red flame in the bottom right? Did you do a Go to Symbol in Workspace?