VS Code freezes and crashes when the Python extension activates on Windows
See original GitHub issueSimilar issues: #6687 #9554 #3967 #5437 #9093
Environment data
- VS Code version: 1.49.3
- Extension version (available under the Extensions sidebar): v2020.9.112786
- OS and version: Windows v2004
- Python version (& distribution if applicable, e.g. Anaconda): 3.8.0 on WSL and 3.8.6 local
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): WSL
- Relevant/affected Python packages and their versions: –
- Relevant/affected Python-related VS Code extensions and their versions: ms-python Python extension
- Value of the
python.languageServer
setting: Pylance
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
Python extension loads when .py file is opened or created and VS code continues to function
Actual behaviour
“Python extension loading” appears then eventually VS code freezes and crashes or disconnects me from my remote WSL environment
Steps to reproduce:
1.Open vs code 2.Open or create a .py file with the Python extension installed and enabled
Logs
When I follow these steps running vs code locally it freezes and crashes. When I run them on WSL: Ubuntu it eventually disconnects which forces me to close. I don’t see anything in the output panel before it freezes. Occasionally a new file will open called “Getting Started -Python” right before VS code freezes.
I am relatively new [to vscode and development] so if there is some output you think exists it is likely that I just don’t know how to get to it without being told.
Thank you for your help…
Andrew Noel
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (1 by maintainers)
Top GitHub Comments
Sorry for the delay, I’ll try to get this done later today thank you.
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.