ProcessPoolExecutor deadlock on KeyboardInterrupt

Open
#70,096 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading worker_ignore_interrupt.patch and the dependency on bpo-22393, then inspect the available issue messages for reproduction details about the ProcessPoolExecutor deadlock. Done should mean a reproducible regression test and a verified fix for KeyboardInterrupt handling without the executor hanging.

Written by the indexing model from the issue text.

Description

topic-multiprocessing type-bug
BPO 25908
Nosy @applio
Dependencies
  • bpo-22393: multiprocessing.Pool shouldn't hang forever if a worker process dies unexpectedly
    		•
    Files
  • worker_ignore_interrupt.patch
    		•

    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 2015-12-18.19:41:10.721>
labels = ['type-bug']
title = 'ProcessPoolExecutor deadlock on KeyboardInterrupt'
updated_at = <Date 2015-12-27.17:11:24.197>
user = 'https://bugs.python.org/jacksontj'

    bugs.python.org fields:

    activity = <Date 2015-12-27.17:11:24.197>
actor = 'davin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-12-18.19:41:10.721>
creator = 'jacksontj'
dependencies = ['22393']
files = ['41358']
hgrepos = []
issue_num = 25908
keywords = ['patch']
message_count = 4.0
messages = ['256703', '256705', '256711', '257085']
nosy_count = 2.0
nosy_names = ['davin', 'jacksontj']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25908'
versions = ['Python 2.7', 'Python 3.5', '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.