[issue40402] Race condition in multiprocessing/connection.py: broken handle

STINNER Victor added the comment: See also bpo-39995: race condition in concurrent.futures. More specific to _ThreadWakeup class, but with similar symptoms. -- nosy: +vstinner ___ Python tracker

[issue40402] Race condition in multiprocessing/connection.py: broken handle

Change by Rémi Lapeyre : -- keywords: +patch pull_requests: +19113 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/19790 ___ Python tracker

[issue40402] Race condition in multiprocessing/connection.py: broken handle

Antoine Pitrou added the comment: I don't know if a try..except block is the best solution, but feel free to submit a PR and we can iterate on that :-) -- stage: -> needs patch ___ Python tracker

[issue40402] Race condition in multiprocessing/connection.py: broken handle

Rémi Lapeyre added the comment: A call to self._check_closed() is already present in Python 3.5 https://github.com/python/cpython/blob/3.5/Lib/multiprocessing/connection.py#L202-L206 It is possible for some issues to appear when mixing multiprocessing and multithreading thought: In [17]: