multiprocessing.util._afterfork_registry leak in threaded environment

未关闭
#70,368 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
backend, performance

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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']

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue，再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库，在一个分支上完成修改。
    4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。