python3 multiprocessing queue deadlock when use thread and process at same time

Open
#79,789 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend, operating-systems

Research direction

No source file or test is named in the report. Start by reading BPO 35608 and its eight-message discussion, then locate the multiprocessing queue path involved; done requires reproducing the reported deadlock and verifying that the open issue's behavior is addressed.

Written by the indexing model from the issue text.

Description

stdlib topic-multiprocessing type-bug
BPO 35608
Nosy @tim-one, @pitrou, @applio, @eamanu, @ruozeng-w

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 2018-12-29.02:53:42.097>
labels = ['type-bug', 'library']
title = 'python3 multiprocessing queue deadlock when use thread and process at same time'
updated_at = <Date 2020-10-20.08:13:00.437>
user = 'https://bugs.python.org/beruhan'

bugs.python.org fields:

activity = <Date 2020-10-20.08:13:00.437>
actor = 'dukewrz'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-12-29.02:53:42.097>
creator = 'beruhan'
dependencies = []
files = []
hgrepos = []
issue_num = 35608
keywords = []
message_count = 8.0
messages = ['332691', '332694', '332695', '332706', '332710', '332723', '332850', '379101']
nosy_count = 6.0
nosy_names = ['tim.peters', 'pitrou', 'davin', 'eamanu', 'beruhan', 'dukewrz']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35608'
versions = ['Python 3.6']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.