VSCode is slow and occupying a large amount of memory

[Djinhui]

My Windows PC VSCode is the latest version 1.103, and currently there are the following issues:

1. 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
2. When manually selecting a Python interpreter, it takes a long time to discover and refresh Python interpreters
3. 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
4. When running Python files, you have to wait for a while before they actually run
5. After opening a VSCode window, opening a new VSCode window may be slow or result in an error message that cannot be opened
6. 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
7. 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)

[eleanorjboyd]

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

[hy-0003]

I meet the same trouble.Has this problem been solved?

[hy-0003]

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