From 38f23604c19d357d9782eb2c1a740c3296c08890 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
 <31488909+miss-islington@users.noreply.github.com>
Date: Wed, 31 Dec 2025 00:29:56 +0100
Subject: [PATCH] [3.14] gh-115634: document ProcessPoolExecutor
 max_tasks_per_child bug (GH-140897) (#143302)

gh-115634: document ProcessPoolExecutor max_tasks_per_child bug (GH-140897)
(cherry picked from commit 04899b8539ab83657a4495203f26b3cb1a6f46dc)

Co-authored-by: Gregory P. Smith <68491+gpshead@users.noreply.github.com>
---
 Doc/library/concurrent.futures.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst
index c2e2f7f820f..18d92e8e995 100644
--- a/Doc/library/concurrent.futures.rst
+++ b/Doc/library/concurrent.futures.rst
@@ -379,6 +379,11 @@ in a REPL or a lambda should not be expected to work.
    default in absence of a *mp_context* parameter. This feature is incompatible
    with the "fork" start method.
 
+   .. note::
+      Bugs have been reported when using the *max_tasks_per_child* feature that
+      can result in the :class:`ProcessPoolExecutor` hanging in some
+      circumstances. Follow its eventual resolution in :gh:`115634`.
+
    .. versionchanged:: 3.3
       When one of the worker processes terminates abruptly, a
       :exc:`~concurrent.futures.process.BrokenProcessPool` error is now raised.