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 davin
Recipients davin, pablogsal, pitrou, steve.dower, vstinner
Date 2019-09-10.15:38:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sharing for the sake of documenting a few things going on in this particular example:
* When a PoolWorker process exits in this way (os._exit(anything)), the PoolWorker never gets the chance to send a signal of failure (normally sent via the outqueue) to the MainProcess.
* In the current logic of the MainProcess, Pool._maintain_pool() detects the termination of that PoolWorker process and starts a new PoolWorker process to replace it, maintaining the desired size of Pool.
* The infinite hang observed in this example comes from the original call performing an unlimited-timeout wait for a result to appear on the outqueue, hence an infinite wait.  This wait is performed in MapResult.get() which does expose a timeout parameter though it is not possible to control through  It is not at all a correct, general solution, but exposing the control on this timeout and setting it to 1.0 seconds permits Steve's repro code snippet to run to completion (no infinite hang, raises a multiprocessing.context.TimeoutError).
Date User Action Args
2019-09-10 15:38:20davinsetrecipients: + davin, pitrou, vstinner, steve.dower, pablogsal
2019-09-10 15:38:20davinsetmessageid: <>
2019-09-10 15:38:20davinlinkissue38084 messages
2019-09-10 15:38:20davincreate