Goto Definition takes a couple of seconds each time to complete the jump about vscode-cpptools HOT 3 OPEN

Thank you for opening this issue. I think there is something unusual going on, because this operation is nearly instantaneous for me after copying your code into a C file.

The main contributor to the slowness is that the extension is choosing to do "Find all References" instead of "Go to Definition." Would you be able to enable Debug logging, restart the extension, rerun your scenario and then share the logs with us?

from vscode-cpptools.

Thank you for your reply. Please see the attached log.

I performed 4-5 "goto definition" actions this time, 3 of which are instantaneous, the other 2 suffer from the problem depicted in my original video (all 5 goto definitions jump to inside either winuser.h or windef.h).

I did not perform any "find all references" action, but the LSP seems to have received/invoked lots of cpptools/findAllReferences action.

debug.log

I'm going to try and see if I can get a cleaner log and if so I'll post it here.

from vscode-cpptools.

Hi @yg-i,

I'm looking at your log and I see multiple "Find all References" requests. I had thought that maybe what was happening was that VS Code was translating your "Go To Definition" request into a "Find all References" request. This happens by default when we return the current location as the result which can happen when we haven't located the actual definition. However, when this happens, I should see a "Go To Definition" request in the log right before the "Find all References" request and I don't see that.

Do you happen to have any extensions installed that automatically invoke "Find all References" as you move the cursor around? Most of the calls to "Find all References" seem to be happening right after moving the cursor, or opening a file (which also sets the cursor position).

from vscode-cpptools.