From 6d5f9e73d973a9ec5a68dfc0bc1859e6e4f50896 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Charles-Fran=C3=A7ois=20Natali?= Date: Sun, 18 Dec 2011 18:35:09 +0100 Subject: [PATCH] Issue #11870: threading: Properly reinitialize threads internal locks and condition variables to avoid deadlocks in child processes. --- Lib/threading.py | 11 ++++------- Misc/NEWS | 3 +++ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Lib/threading.py b/Lib/threading.py index 6653f6ef65..043e6c82af 100644 --- a/Lib/threading.py +++ b/Lib/threading.py @@ -1068,21 +1068,18 @@ def _after_fork(): current = current_thread() with _active_limbo_lock: for thread in _active.values(): + # Any lock/condition variable may be currently locked or in an + # invalid state, so we reinitialize them. + thread._reset_internal_locks() if thread is current: # There is only one active thread. We reset the ident to # its new value since it can have changed. ident = _get_ident() thread._ident = ident - # Any condition variables hanging off of the active thread may - # be in an invalid state, so we reinitialize them. - thread._reset_internal_locks() new_active[ident] = thread else: # All the others are already stopped. - # We don't call _Thread__stop() because it tries to acquire - # thread._Thread__block which could also have been held while - # we forked. - thread._stopped = True + thread._stop() _limbo.clear() _active.clear() diff --git a/Misc/NEWS b/Misc/NEWS index 72b33b99f3..4be3a6b6f8 100644 --- a/Misc/NEWS +++ b/Misc/NEWS @@ -97,6 +97,9 @@ Core and Builtins Library ------- +- Issue #11870: threading: Properly reinitialize threads internal locks and + condition variables to avoid deadlocks in child processes. + - Issue #8035: urllib: Fix a bug where the client could remain stuck after a redirection or an error. -- 2.40.0