Garbage Collection makes some object live for very long
未關閉
還沒有人認領這個 Issue。
3.12
interpreter-core
performance
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- PR 合併指標
- PR 指標待擷取
描述
| BPO | 39061 |
|---|---|
| Nosy | @pablogsal, @mistasse |
| Files |
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 2019-12-16.10:01:34.949>
labels = ['interpreter-core', 'performance']
title = 'Garbage Collection makes some object live for very long'
updated_at = <Date 2019-12-16.19:06:33.825>
user = 'https://github.com/mistasse'
bugs.python.org fields:
activity = <Date 2019-12-16.19:06:33.825>
actor = 'pablogsal'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-12-16.10:01:34.949>
creator = 'mistasse'
dependencies = []
files = ['48780']
hgrepos = []
issue_num = 39061
keywords = []
message_count = 4.0
messages = ['358469', '358486', '358488', '358491']
nosy_count = 2.0
nosy_names = ['pablogsal', 'mistasse']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue39061'
versions = []
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先執行附帶的 late_gc.py 範例,以重現不必要的記憶體增長。接著追蹤 interpreter-core 中與物件存活時間超過必要時長有關的垃圾回收行為。完成的標準是找出原因,並證明該範例不再出現所回報的物件存活時間過長或記憶體增長問題。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- performance
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100