From 20ec2b7710243375c8eeeb4a09b3c1e9d16cd32c Mon Sep 17 00:00:00 2001
From: "Gregory P. Smith" <greg@krypto.org>
Date: Sun, 2 Nov 2025 03:34:23 +0000
Subject: [PATCH] gh-115634: document ProcessPoolExecutor max_tasks_per_child
 bug

---
 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 c2e2f7f820f4ef..18d92e8e9959a9 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.