This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tzickel
Recipients Windson Yang, benjamin.peterson, davin, docs@python, mattip, ned.deily, pablogsal, pitrou, tzickel, vstinner, zach.ware
Date 2018-12-03.17:31:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The previous posts here touch all this subjects:
A. The documentation explicitly says: "When the pool object is garbage collected terminate() will be called immediately." (Happened till a code refactor 9 years ago introduced this bug).

B. Large amount of code was developed for this technique: (Till the end of the file almost)

C. The reason I opened this bug was because I was called to see why a long running process crashes after a while, and found out it leaked tons of subprocesses / pool._cache memory.

D. The quoted code, will currently simply leak each invocation lots of subprocesses... 

I too, think we should push for the said fix.
Date User Action Args
2018-12-03 17:31:12tzickelsetrecipients: + tzickel, pitrou, vstinner, benjamin.peterson, ned.deily, docs@python, zach.ware, mattip, davin, pablogsal, Windson Yang
2018-12-03 17:31:12tzickelsetmessageid: <>
2018-12-03 17:31:12tzickellinkissue34172 messages
2018-12-03 17:31:12tzickelcreate