ProcessPoolExecutor executor manager thread crashes if task fails in some circumstances
Offen
@gpshead arbeitet bereits daran.
Seit 03.7.2026.
3.13
3.14
stdlib
topic-multiprocessing
type-bug
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 35.9k
- PR-Merge-Kennzahlen
- PR-Kennzahlen ausstehend
Beschreibung
Bug report
Bug description:
import time
from concurrent.futures import ProcessPoolExecutor
def fail():
time.sleep(1)
raise ValueError()
executor = ProcessPoolExecutor(max_workers=1, max_tasks_per_child=1)
try:
print(executor.submit(fail).exception() is not None)
finally:
executor.shutdown(wait=False)
If you run this, then the following is printed to the console:
Exception in thread Thread-1:
Traceback (most recent call last):
File "python3.11/threading.py", line 1045, in _bootstrap_inner
self.run()
File "python3.11/concurrent/futures/process.py", line 364, in run
executor._adjust_process_count()
File "python3.11/concurrent/futures/process.py", line 759, in _adjust_process_count
process_count = len(self._processes)
^^^^^^^^^^^^^^^^^^^^
TypeError: object of type 'NoneType' has no len()
If you change the code to using wait=True, or remove the max_tasks_per_child=1 option then the message is not printed.
Probably the fix is just to check if self.processes is None before accessing it at https://github.com/python/cpython/blob/main/Lib/concurrent/futures/process.py#L762
CPython versions tested on:
3.11
Operating systems tested on:
Linux
Linked PRs
- gh-152978
- gh-153363
- gh-154873
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.