python process will be killed when project window activating conda environment

[XZLancer]

Type: Bug

Behaviour

I encounterd a weird problem, whenever I open a project window (with remote-SSH), normally, a conda environment starts activating, but at this time the processes using the conda environments (other environments and the activating one) will be killed. Such processes include pytorch training, jupyter notebook and even conda install command.

I'm using VS code 1.99.3, the latest python extensions and the latest anaconda. Thanks for any help.

Steps to reproduce:

1. For example, open a project window and start a python process, then reload this window. At that time I can see the process be killed. I have checked dmesg | grep kill, it is not a resouce limitation problem.

Diagnostic data

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

The only error I see in `Output-Pyhon` is below:

[error] Failed to initialize deactivate script /bin/bash [Error: "/home/user/.vscode-server/extensions/ms-python.python-2025.4.0-linux-x64/python_files/deactivate/bash/envVars.txt" file not created
	at Timeout.<anonymous> (/home/user/.vscode-server/extensions/ms-python.python-2025.4.0-linux-x64/out/client/extension.js:2:310591)
	at listOnTimeout (node:internal/timers:581:17)
	at process.processTimers (node:internal/timers:519:7)]

Extension version: 2025.4.0
VS Code version: Code 1.99.3 (17baf841131aa23349f217ca7c570c76ee87b957, 2025-04-15T23:18:46.076Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.4.0-212-generic
Remote OS version: Linux x64 5.4.0-204-generic
Remote OS version: Linux x64 5.4.0-204-generic

[XZLancer]

I found the error message in Output-Server when the crash happens:

[error] [File Watcher] Inotify limit reached (ENOSPC) (path: /home/user/anaconda3/envs/torch-latest/lib/python3.9)

and the error in Output-Jupyter(The following is the complete log, there is no information after 'Reason:'):

[error] Disposing session as kernel process died ExitCode: undefined, Reason:

Is there any other useful information I can provide?

[karthiknadig]

@DonJayamanne Is this something that Jupyter needs to investigate?

[DonJayamanne]

then reload this window. At that time I can see the process be killed

This is expected. f you reload VSCode, then all processes started by VS Code will be killed.
Same with Jupyter kernels and the like.

The only process that survive reloading VS Code are terminal sessions.
https://code.visualstudio.com/docs/terminal/advanced#_persistent-sessions

If you want Jupyter Kernels in VS Code Notebooks to persist, then please upvote & follow this issue microsoft/vscode-jupyter#3998

@karthiknadig
Not sure what the following error means though
Failed to initialize deactivate script /bin/bash [Error: "/home/user/.vscode-server/extensions/ms-python.python-2025.4.0-linux-x64/python_files/deactivate/bash/envVars.txt" file not created at Timeout.<anonymous> (/home/user/.vscode-server/extensions/ms-python.python-20

[XZLancer]

This is expected. f you reload VSCode, then all processes started by VS Code will be killed.

The process not related to VS Code (e.g. a shell command like python script.py in a standalone terminal) will also be killed when a VS Code window starts activating environment.

However, this problem suddenly disappeared after a few days, during which time VS Code and extensions were not updated. Maybe it's a system problem, I will close the issue, thank you for your attention