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

YAML - !Yet another memory leak! Opened a PR to fix the non exisiting issue #754

Closed
shoaib42 opened this issue Aug 10, 2024 · 1 comment
Closed

Comments

@shoaib42
Copy link

Can someone from the maintainers check the PR I created. Its a simple addition to multiprocessing doc. The RCA is not DEAP but the simple quickstart that most follow. #753

@fmder
Copy link
Member

fmder commented Aug 12, 2024

This is not an issue with deap but with the general understanding of multiprocessing. It does not just happen with deap, but with any combination of libraries using multiprocessing/threading. It also happens when you combine torch multi loader and numpy. I dont think a warning in comment will help, but this issue might be a better place.

So beware, whe using multiprocessing any underlying library might also launch N processes/threads based on some environment variable or else. In case of numpy the most common environment variables to control the number of threads are OMP_NUM_THREADS and MKL_NUM_THREADS.

@fmder fmder closed this as completed Aug 12, 2024
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