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

pipenv update created too many subprocess until crash #3832

Closed
yixblog opened this issue Jul 10, 2019 · 5 comments

Comments

@yixblog
Copy link

commented Jul 10, 2019

I installed new python3.7.4 amd64 into Windows 10 Home OS

And installed pipenv by pip install pipenv

But when I was initializing my python projects with pipenv update command (pipenv install also tried). The command screen shows creating virtualenv and keeping creating huge number of sub process until the system got out of memory or just crashed.

pipenv
As this image shows, the number of subprocess is increasing very fast until took down all CPU and Memory resources but did nothing. I cannot even init a new project. I don't know if there were any mistake.

@yixblog

This comment has been minimized.

Copy link
Author

commented Jul 10, 2019

And the previous mistake in the image is caused by command: pipenv --py

@akittas

This comment has been minimized.

Copy link

commented Jul 10, 2019

The problem is probably related to this virtualenv issue. For the moment the solution is to downgrade to Python 3.7.3, as it happens only with 3.7.4.

@yixblog

This comment has been minimized.

Copy link
Author

commented Jul 10, 2019

The problem is probably related to this virtualenv issue. For the moment the solution is to downgrade to Python 3.7.3, as it happens only with 3.7.4.

solved! thanks a lot! This troubles me the entire afternoon

@frostming

This comment has been minimized.

Copy link
Collaborator

commented Jul 11, 2019

Pin this issue for any newcomers who encountered this problem.

@frostming

This comment has been minimized.

Copy link
Collaborator

commented Jul 15, 2019

The fix should be released via https://pypi.org/project/virtualenv/16.6.2/, upgrade virtualenv to >=16.6.2 should fix this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.