[multiprocessing] Calling pool.terminate() from an error_callback causes deadlock
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42963 |
|---|---|
| Nosy | @sjelin |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-01-19.01:08:51.183>
labels = ['3.7', 'type-bug', 'library']
title = '[multiprocessing] Calling pool.terminate() from an error_callback causes deadlock'
updated_at = <Date 2021-01-19.01:10:42.325>
user = 'https://github.com/sjelin'
bugs.python.org fields:
activity = <Date 2021-01-19.01:10:42.325>
actor = 'sjelin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-01-19.01:08:51.183>
creator = 'sjelin'
dependencies = []
files = []
hgrepos = []
issue_num = 42963
keywords = []
message_count = 1.0
messages = ['385240']
nosy_count = 1.0
nosy_names = ['sjelin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42963'
versions = ['Python 3.6', 'Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the multiprocessing Pool behavior around terminate() and error_callback, then reproduce the reported deadlock described in the issue title. The payload names no source file or test, so locating the relevant implementation and regression-test entry point will require repository research. Done means pool.terminate() invoked from an error_callback no longer deadlocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100