multiprocessing.get hangs if the pool is closed in the signal handler
Open
Nobody has claimed this yet.
3.10
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 44462 |
|---|---|
| Nosy | @chaitu-tk |
| Files |
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-06-19.19:49:48.653>
labels = ['type-bug', 'library', '3.10']
title = 'multiprocessing.get hangs if the pool is closed in the signal handler'
updated_at = <Date 2021-06-19.19:49:48.653>
user = 'https://github.com/chaitu-tk'
bugs.python.org fields:
activity = <Date 2021-06-19.19:49:48.653>
actor = 'tkc17'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-06-19.19:49:48.653>
creator = 'tkc17'
dependencies = []
files = ['50121']
hgrepos = []
issue_num = 44462
keywords = []
message_count = 1.0
messages = ['396151']
nosy_count = 1.0
nosy_names = ['tkc17']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44462'
versions = ['Python 3.10']
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
Read and run the reproduction script in mp_test.py to observe the hang when multiprocessing.get is used after the pool is closed in a signal handler. Trace the multiprocessing and signal-handling path responsible for the wait, then add coverage for the reported scenario and verify that the call completes without hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100