GC - Possible to indefinitely prevent collection of generation-1 objects by calling gc.collect(0) often
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 35.9k
- PR 合并指标
- PR 指标待抓取
描述
Bug report
Bug description:
The example below will die from memory exhaustion, despite nearly all objects being eligible for collection and despite garbage collection not being disabled. See inline comments for an explanation of what I think is happening:
import gc
from typing import Any
class Temp:
def __init__(self):
# Cyclic reference to prevent deletion by ref count dropping to 0.
self._x = self
# Allocate a bunch of memory so that the process will die if
# collection doesn't happen.
self.memory = bytearray(1024*1024*512)
# Set some low thresholds so that collection should occur often.
gc.set_threshold(100, 3, 3)
while True:
ref = Temp()
# Promote the new Temp() object to generation-1. I think this is also resetting
# the GCs view of how many objects were allocated at the "last collection". If
# that's true, it will effectively stop the GC from ever being invoked
# automatically, even though we're accumulating more and more objects,
# because `threshold0` will never be exceeded.
gc.collect(0)
del ref
# Temp() is now in generation-1 and eligible for collection, but gc.collect(1)
# is never triggered, because there are no automatically invoked GCs at all.
# Here we log the number of generation-1 objects, which continues to increase
# until the process dies.
print("Number of generation 1 objects: ", len(gc.get_objects(generation=1)))
Commenting out only the gc.collect(0) allows the Temp objects to be collected, and the process to run indefinitely. The fact that removing an explicit GC actually enables more GC to happen seems broken.
If what I think is happening is what's happening, then perhaps manually invoked GCs should not reset the GC's view on how many objects were allocated at the "last collection", since that would be what's effectively disabling the automatically triggered GCs (and hence the GCs at higher generations) from running.
CPython versions tested on:
3.11
Operating systems tested on:
macOS
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未指定源文件或测试。首先在 CPython 3.11 上运行提供的复现程序,并跟踪 gc.collect(0) 的行为、自动收集阈值以及 generation-1 的增长。确认报告中的交互行为,并在验证该行为后添加适当的回归测试和修复,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- backend
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100