Add helpful hints to multiprocess doc for avoiding mem leaks #753
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently ran into an issue with multiprocessing and memleaks. The system chewed up 32GB or ram and then some 2 GB of swap, with 2 gens left to finish, after some 4 hours of darwin chugging silicon oil.
I've noticed a few open issues complaining about mem leak while using multiprocessing.
The issue is noticed when libs like tensorflow are used, that have a mind of their own. Clearing up the session/explicit gc/del model or anything besides terminating the process doesn't help.
I think the addition of code sample in the doc will help many avoid this. And avoid issues being created for mem leak.