multiprocessing.Queue deadlock
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41714 |
|---|---|
| Nosy | @pitrou, @applio, @rpurdie |
| 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 2020-09-04.10:19:47.036>
labels = ['library', 'type-crash']
title = 'multiprocessing.Queue deadlock'
updated_at = <Date 2020-09-07.23:44:27.232>
user = 'https://github.com/rpurdie'
bugs.python.org fields:
activity = <Date 2020-09-07.23:44:27.232>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-09-04.10:19:47.036>
creator = 'rpurdie'
dependencies = []
files = ['49444']
hgrepos = []
issue_num = 41714
keywords = []
message_count = 3.0
messages = ['376350', '376351', '376357']
nosy_count = 3.0
nosy_names = ['pitrou', 'davin', 'rpurdie']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue41714'
versions = ['Python 3.6']
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 and running the linked simplified.py reproducer, then inspect the multiprocessing.Queue behavior involved in the deadlock. The issue is complete when the reported deadlock is understood and resolved with a regression test, but the payload does not identify the relevant implementation or test files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100