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

Segfault on a significant percentage of conda installs #5014

Closed
goerz opened this issue Dec 18, 2018 · 4 comments
Closed

Segfault on a significant percentage of conda installs #5014

goerz opened this issue Dec 18, 2018 · 4 comments
Labels
Status: stale Issue will be considered inactive soon Support Support question

Comments

@goerz
Copy link

goerz commented Dec 18, 2018

For a significant number of builds (somewhere between 10-30% would be my estimate), builds that use conda fail with a segfault. Example: https://readthedocs.org/projects/weylchamber/builds/8294985/

I'm seeing the same behavior across all my projects.

@stsewd
Copy link
Member

stsewd commented Dec 18, 2018

Conda is very heavy (consumes a lot of memory and time), there isn't much we can do. Same issue as #4574

@stsewd stsewd added the Support Support question label Dec 18, 2018
@msarahan
Copy link

msarahan commented Dec 19, 2018

Hi, I'm one of the conda maintainers. Sorry for the headache. The place where this failed is a strange place to run out of memory. At that point, it looks like it is just doing the final copying of files. We'll look into it and hopefully reduce the memory consumed by conda.

We are in the early stages of monitoring performance and memory usage using air speed velocity. Our benchmarks are at https://conda.github.io/conda-benchmarks/

None of those benchmarks run the part where the crash is reported here, because we had assumed it is just disk operations and not terribly interesting to benchmark. I think we will add that part in.

@stsewd
Copy link
Member

stsewd commented Dec 19, 2018

@msarahan those are great news! thanks!

@stale
Copy link

stale bot commented Feb 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Feb 2, 2019
@stale stale bot closed this as completed Feb 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: stale Issue will be considered inactive soon Support Support question
Projects
None yet
Development

No branches or pull requests

3 participants