[issue30006] Deadlocks in `concurrent.futures.ProcessPoolExecutor`

Antoine Pitrou added the comment: Ok, closing as duplicate then. -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> Deadlocks in `concurrent.futures.ProcessPoolExecutor` with pickling error ___ Pytho

[issue30006] Deadlocks in `concurrent.futures.ProcessPoolExecutor`

Thomas Moreau added the comment: The deadlocks I refer to in this issue are fixed by the PR #3895. Subsequent failures (like the fact that the Executor is set in a broken state when there is an unpickling error) are tracked in other issues so I think it is safe to close this one. --

[issue30006] Deadlocks in `concurrent.futures.ProcessPoolExecutor`

Brian Quinlan added the comment: Was this fixed by https://github.com/python/cpython/pull/3895 ? -- ___ Python tracker ___ ___ Pyth

[issue30006] Deadlocks in `concurrent.futures.ProcessPoolExecutor`

Changes by Antoine Pitrou : -- nosy: +bquinlan, davin, pitrou stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mail

[issue30006] Deadlocks in `concurrent.futures.ProcessPoolExecutor`

New submission from Thomas Moreau: The design of ProcessPoolExecutor contains some possible race conditions that may freeze the interpreter due to deadlocks. This is notably the case with pickling and unpickling errors for a submitted job and returned results. This makes it hard to reuse a la