You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VSCode is slow and occupying a large amount of memory #25395
My Windows PC VSCode is the latest version 1.103, and currently there are the following issues:
The default interpreter for Python has already been set, but after opening the Python file, you still need to manually select the Python interpreter, or it may take a long time for the default interpreter to be automatically selected
When manually selecting a Python interpreter, it takes a long time to discover and refresh Python interpreters
Even if a Python interpreter has been selected in the current Python file, when a new Python file is opened, it will still take some time for the new Python file to display the Python interpreter
4.After opening the Python file, the Python interpreter has also been selected, but it takes a long time for the syntax in the Python file to be highlighted
When running Python files, you have to wait for a while before they actually run
After opening a VSCode window, opening a new VSCode window may be slow or result in an error message that cannot be opened
After opening VSCode, even if the program is not allowed, many child processes will still open in the background of VSCode, occupying a large amount of memory
VSCode display Pty Host,The connection to the terminal's pty host process is unresponsive.Click to manually restart the pty host
The plugin I installed in VSCode is: CodeGeeX、Jupyter、Jupyter Cell Tags、Jupyter Keymap、Jupyter Notebook Rendeners、Jupyter Slide Show、Pylance、Python、Python Debugger、Python Environments
Please help me analyze the causes of these problems and provide solutions (I have tried uninstalling and reinstalling VSCode, but still have these issues)
Hi! Can you try setting python.useEnvironmentsExtension setting to false and see if that causes your problem to resolve? If so it is caused by our new environment extension which I can then go through and debug
Hi! Can you try setting python.useEnvironmentsExtension setting to false and see if that causes your problem to resolve? If so it is caused by our new environment extension which I can then go through and debug
I've tried it, but the effect hasn't changed.My plugin :Chinese、Github copilot、Live Server、Python、Pylance、Python Debugger、Python Environments
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.
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.
🤖 Thanks for the report and for confirming that the problem persists. To isolate the cause, please reproduce this on the latest VS Code and extension releases and provide the Python version and environment manager, the output from Python: Report Issue, relevant logs from the Python output channel, and timings or Process Explorer data showing which process is consuming memory. Please also use Extension Bisect or test with only the Python extension enabled, and clarify which symptoms remain in that configuration. Issues marked info-needed are automatically closed after 30 days without a reply.
Activity
eleanorjboyd commentedon Aug 18, 2025
Hi! Can you try setting
python.useEnvironmentsExtensionsetting to false and see if that causes your problem to resolve? If so it is caused by our new environment extension which I can then go through and debughy-0003 commentedon Aug 20, 2025
I meet the same trouble.Has this problem been solved?
hy-0003 commentedon Aug 20, 2025
I've tried it, but the effect hasn't changed.My plugin :Chinese、Github copilot、Live Server、Python、Pylance、Python Debugger、Python Environments
github-actions commentedon Sep 20, 2025
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
Djinhui, you can help us out by closing this issue if the problem no longer exists, or adding more information.
github-actions commentedon Oct 20, 2025
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.
Happy Coding!
github-actions commentedon Nov 30, 2025
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.
Happy Coding!
eleanorjboyd commentedon Sep 23, 2026
🤖 Thanks for the report and for confirming that the problem persists. To isolate the cause, please reproduce this on the latest VS Code and extension releases and provide the Python version and environment manager, the output from
Python: Report Issue, relevant logs from the Python output channel, and timings or Process Explorer data showing which process is consuming memory. Please also use Extension Bisect or test with only the Python extension enabled, and clarify which symptoms remain in that configuration. Issues markedinfo-neededare automatically closed after 30 days without a reply.