Gets stuck at "Python extension loading" then extension host crashes when `telemetry.enableTelemetry` is set to `false`
See original GitHub issueThere’s a few other mentions of this but no fixes so far.
Environment data
- VS Code version: Noticed after upgrade to 1.52, kept happening after downgrade to 1.51.
- Extension version (available under the Extensions sidebar): v2020.12.422005962
- OS and version: Windows 10 2004
- Python version (& distribution if applicable, e.g. Anaconda): 3.9, same on 3.91
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
- Relevant/affected Python packages and their versions: All
- Relevant/affected Python-related VS Code extensions and their versions: Base Python extension
- Value of the
python.languageServer
setting: Pylance
Expected behaviour
Message disappears and extension eventually loads.
Actual behaviour
Message doesn’t disappear, extension doesn’t load, “Extension host terminated unexpectedly” message appears.
Steps to reproduce:
- Start VSCode
- Select a python file to trigger the extension loading.
Was also able to reproduce after separately:
- reinstalling VScode
- recreating %userprofile%.vscode
- recreating %appdata%\Code
- Updating python to 3.91
- Enabling only the Python extension
Logs
Total output of OUTPUT > Python. Extension host crashes after it sits at this for a while.
Info 2020-12-15 16:12:53: Searching for workspace virtual envs in: d:\users\ben\Documents\advent-of-code-2020
Info 2020-12-15 16:12:53: Searching for workspace virtual envs in: d:\users\ben\Documents\advent-of-code-2020\.direnv
Info 2020-12-15 16:12:53: Searching for global virtual envs in: C:\Users\Ben\Envs
Info 2020-12-15 16:12:53: Searching for global virtual envs in: C:\Users\Ben\.direnv
Info 2020-12-15 16:12:53: Searching for global virtual envs in: C:\Users\Ben\.venvs
Info 2020-12-15 16:12:53: Searching for global virtual envs in: C:\Users\Ben\.virtualenvs
Info 2020-12-15 16:12:53: Searching for global virtual envs in: C:\Users\Ben\.local\share\virtualenvs
User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonSendEntireLineToREPLcf'
Issue Analytics
- State:
- Created 3 years ago
- Reactions:15
- Comments:74 (10 by maintainers)
Top Results From Across the Web
How to solve the problem"Python extension loading..." in ...
Try to disable telemetry in the user settings: "telemetry.enableTelemetry": false,.
Read more >Junos OS Release Notes for MX Series - Juniper Networks
These release notes accompany Junos OS Release 20.2R3 for the MX Series. They describe new and changed features, limitations, and known and resolved ......
Read more >Migrating from IntelliJ IDEA to VSCode and Metals - Iterators
Installing VSCode and Metals is pretty straightforward – you can download it here, and then go to Extensions ( Ctrl+Alt+X ) and install ......
Read more >Vscode Python Extension Cannot Find Python After Update ...
Gets stuck at Python extension loading then extension host crashes when telemetry.enableTelemetry is set to false #14977. Closed.
Read more >Release Notes for Cisco Identity Services Engine, Release 3.0
An administrator can then use this information to make proactive ... Cisco ISE PSN nodes crash due to incorrect cryptoLib initialization.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had same issue too
Version: 1.56.0 (user setup) Commit: cfa2e218100323074ac1948c885448fdf4de2a7f Date: 2021-05-04T22:09:06.405Z Electron: 12.0.4 Chrome: 89.0.4389.114 Node.js: 14.16.0 V8: 8.9.255.24-electron.0 OS: Windows_NT x64 10.0.19041
Python : 3.8.10
"telemetry.enableTelemetry": false
Hi all,
You can temporarily fix this by adding following User setting as a workaround:
But in order to fix it properly, we need more info:
User belongs to experiment group
which are important to us: Please provide the above info before using the workaround, thanks!