Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault when using conda #11094

Closed
2 tasks done
zixuzixu opened this issue Jan 30, 2024 · 3 comments
Closed
2 tasks done

Segmentation fault when using conda #11094

zixuzixu opened this issue Jan 30, 2024 · 3 comments

Comments

@zixuzixu
Copy link

zixuzixu commented Jan 30, 2024

Description

I am encountering a segmentation fault error when using Conda on Windows Subsystem for Linux (WSL). This issue persists across different Ubuntu distributions (Ubuntu 22.04 LTS and Ubuntu 20.04) and both WSL versions (WSL 1 and WSL 2). The error predominantly occurs when I attempt to create a new Conda environment with a specified Python version using the conda create command. However, the command occasionally succeeds without any apparent reason, adding to the unpredictability of the issue.

Windows Version

Microsoft Windows [Version 10.0.22621.3085]

WSL Version

WSL version: 2.1.1.0 
Kernel version: 5.15.146.1-2 
WSLg version: 1.0.60 
MSRDC version: 1.2.5105 
Direct3D version: 1.611.1-81528511 
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22621.3085

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.15.146.1-microsoft-standard-WSL2 (root@65c757a075e2) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Jan 11 04:09:03 UTC 2024

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

  • install conda
wget https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh
bash Miniforge3-$(uname)-$(uname -m).sh
source ~/.bashrc
  • create env
conda create -n myenv python=3.10

Expected Behavior

The commands runs correctly without bugs.

Actual Behavior

Segmentation fault

Diagnostic Logs

(base) wsl@DESKTOP-V0DJDRP:~$ conda create -n bid python=3.10
Channels:
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): - Segmentation fault

No response

@zixuzixu
Copy link
Author

I'm uncertain whether this is pertinent, but I stumbled upon a similar issue where a user's laptop had more memory installed than what was supported by their mainboard. A related discussion can be found here: WSL #6325.

For my setup, I have equipped my system with 128GB of memory, and I am using a Z690-A motherboard, which is compatible with up to 128GB of memory. This leads me to question the memory support in WSL—specifically, is there official support or any known limitations when using 64GB or 128GB of memory with WSL?

@ghost
Copy link

ghost commented Jan 30, 2024

You've established that the conda application seg faults. That's not much for us to go on and is sparse little to start an investigation with. You should start an investigation with the application developer: https://github.com/conda/conda, if it turns out that they need something from us, they can come back to us with more descriptive bug.

@ghost ghost closed this as completed Jan 30, 2024
@elsaco
Copy link

elsaco commented Jan 30, 2024

@aivoyager here are the memory limitations in WSL 50% of total memory on Windows or 8GB, whichever is less; on builds before 20175: 80% of your total memory on Windows

See details at https://learn.microsoft.com/en-us/windows/wsl/wsl-config

Try to find what's core dumping on your WSL image. Didn't repro on a new Focal image:

elsaco@texas:~$ conda env list
# conda environments:
#
myenv                    /home/elsaco/.conda/envs/myenv
base                     /opt/miniforge3

elsaco@texas:~$ conda activate myenv
(myenv) elsaco@texas:~$ python --version
Python 3.10.13
(myenv) elsaco@texas:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants