[docs] [issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
STINNER Victor
report at bugs.python.org
Thu Dec 6 05:29:58 EST 2018
STINNER Victor <vstinner at redhat.com> added the comment:
See also bpo-35424: "multiprocessing.Pool: emit ResourceWarning".
I wrote 10986 to fix 2 tests which leak resources.
I have a question. Why do tests have to call "pool.join()" after "with pool:"? When I use a file, I know that the resources are released after "with file:".
Should Pool.__exit__() call Pool.join()?
This question reminds me my fix in socketserver (bpo-31151 and bpo-31233) which leaked processes and threads, and my bug bpo-34037 (asyncio leaks threads).
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________
More information about the docs
mailing list