returning after forking a child thread doesn't call Py_Finalize

Open
#50,891 6 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

3.10 3.11 3.9 (EOL) interpreter-core stdlib topic-subinterpreters type-bug
BPO 6642
Nosy @gpshead, @vstinner, @tiran, @rnk
Dependencies
  • bpo-6643: Throw away more radioactive locks that could be held across a fork in threading.py
    		•
    Files
  • thread_fork_hang.py: Failing fork/threads test case.
  • finalize-patch.diff: Straw man patch to do finalization when returning from a forked child thread.
    		•

    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 = 'https://github.com/rnk'
closed_at = None
created_at = <Date 2009-08-04.18:21:49.307>
labels = ['interpreter-core', 'type-bug', '3.9', '3.10', '3.11', 'expert-subinterpreters', 'library']
title = "returning after forking a child thread doesn't call Py_Finalize"
updated_at = <Date 2021-12-12.19:10:33.814>
user = 'https://github.com/rnk'

    bugs.python.org fields:

    activity = <Date 2021-12-12.19:10:33.814>
actor = 'iritkatriel'
assignee = 'rnk'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Library (Lib)', 'Subinterpreters']
creation = <Date 2009-08-04.18:21:49.307>
creator = 'rnk'
dependencies = ['6643']
files = ['14646', '14653']
hgrepos = []
issue_num = 6642
keywords = ['patch']
message_count = 5.0
messages = ['91263', '91290', '192367', '192370', '396681']
nosy_count = 6.0
nosy_names = ['gregory.p.smith', 'vstinner', 'christian.heimes', 'rnk', 'neologix', 'sbt']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue6642'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

    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.