multiprocessing.util._afterfork_registry leak in threaded environment

Open
#70,368 6 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

Research direction

Start by reviewing the linked python/cpython#13986 pull request and the attached bug.py and bug3.py reproductions. Use those materials to understand the threaded-environment leak and determine what tests or cleanup behavior establish that the issue is fixed.

Written by the indexing model from the issue text.

Description

3.9 (EOL) stdlib topic-multiprocessing type-bug
BPO 26180
Nosy @terryjreedy, @nirs, @jdemeyer, @applio
PRs
  • python/cpython#13986
  • Files
  • bug.py
  • bug3.py
  • 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 2016-01-22.15:24:46.852>
    labels = ['library', '3.9', 'performance']
    title = 'multiprocessing.util._afterfork_registry leak in threaded environment'
    updated_at = <Date 2019-06-14.07:05:58.650>
    user = 'https://bugs.python.org/mzamazal'
    

    bugs.python.org fields:

    activity = <Date 2019-06-14.07:05:58.650>
    actor = 'mzamazal'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2016-01-22.15:24:46.852>
    creator = 'mzamazal'
    dependencies = []
    files = ['41690', '41706']
    hgrepos = []
    issue_num = 26180
    keywords = ['patch']
    message_count = 6.0
    messages = ['258816', '258850', '258896', '345473', '345524', '345561']
    nosy_count = 5.0
    nosy_names = ['terry.reedy', 'nirs', 'jdemeyer', 'davin', 'mzamazal']
    pr_nums = ['13986']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'resource usage'
    url = 'https://bugs.python.org/issue26180'
    versions = ['Python 3.9']
    

    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.