Go To Definition Very Slow, Often Hangs Indefinitely

Environment data

• VS Code version: 1.30.2
• Extension version (available under the Extensions sidebar): 2018.12.1
• OS and version: Microsoft Windows 10 Pro Version 10.0.17134 Build 17134
• Python version: 2.7.11
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
• Relevant/affected Python packages and their versions: N/A

Expected behaviour

Whilst highlighted over a Symbol, Press f12 or right-click and then click “Go To Definition” after at most a second, the code editor jumps to the definition.

Actual behaviour

More often than not, the process hangs indefinitely, not slowing vscode in any way, but showing the bar representing an async process happening in the background until reload vscode.

Occasionally does go to the definition after a very long wait of up to 2 minutes.

Screen Recording

Steps to reproduce:

1. Open any Python Script
2. Use the “Go To Definition” functionality on any symbol call within the script

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Starting Jedi Python language engine.
##########Linting Output - pylint##########

--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXX

[ericsnowcurrently]

Thanks for letting us know about this, @GeorgeWL. Are you seing this behavior for simple Python files? Also, please try with the latest version of the extension and with the language server. To enable the language server set "python.jediEnabled": false in your settings.json.

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.