Mailman 3 December 2018 - docs

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
by tzickel 02 Dec '18

02 Dec '18

tzickel <icebreak(a)yahoo.com> added the comment: A. It would be nice to add a test that tests this. B. Now that Pool is cleaning up properly, any of it's functions which return another object (like imap's IMapIterator) need to hold a reference to the Pool, so it won't get cleanedup before computing. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34172> _______________________________________

1 0

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
by Pablo Galindo Salgado 02 Dec '18

02 Dec '18

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: This also happens on Linux, hanging in different moments: ❯ ./python test.py Begin 4 [hangs] ❯ ./python test.py Begin 4 3 [hangs] ❯ ./python test.py [hangs] ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34172> _______________________________________

1 0

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
by Pablo Galindo Salgado 02 Dec '18

02 Dec '18

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: Bisecting between 3.7.0(good) and 3.7.1(bad) with the code in my previous commit points to: 97f998a4dfd6db6d867f446daa62445d0782bf39 is the first bad commit commit 97f998a4dfd6db6d867f446daa62445d0782bf39 Author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> Date: Tue Oct 2 14:17:04 2018 -0700 bpo-34172: multiprocessing.Pool leaks resources after being deleted (GH-8450) (GH-9676) Fix a reference issue inside multiprocessing.Pool that caused the pool to remain alive if it was deleted without being closed or terminated explicitly. (cherry picked from commit 97bfe8d3ebb0a54c8798f57555cb4152f9b2e1d0) Co-authored-by: tzickel <tzickel(a)users.noreply.github.com> :040000 040000 90e0af29e82d0fcc1c1d7e19b3659f9602596e3e d997cfb00c1c44bbd87ce15edfd391203362a1d7 M Lib :040000 040000 6aa4273821c2c563ea69370a59284ed48576416f b6d46f14b6bb36cc5ae62b3ca74025c24d683bb5 M Misc bisect run success ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34172> _______________________________________

1 0

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
by Pablo Galindo Salgado 02 Dec '18

02 Dec '18

Pablo Galindo Salgado <pablogsal(a)gmail.com> added the comment: multiprocessing.Pool.imap hangs in MacOs after applying this commit: import multiprocessing def the_test(): print("Begin") for x in multiprocessing.Pool().imap(int, ["4", "3"]): print(x) print("End") the_test() This also happens in the backported branches. ---------- nosy: +pablogsal status: closed -> open _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34172> _______________________________________

1 0