Asset build: the build process's heap grows to 2 GB
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, javascript, nodejs, python
- 领域
- performance, tooling
调研方向
The growing heap is in the node process of the full asset build; the payload names no file paths. Start by running the build at SRO_BUILD_JOBS=2 with NODE_OPTIONS=--max-old-space-size=1024 under the per-second profiler, then check whether it finishes. If it fails, take a heap snapshot at the claim audit and inspect the publication ledger's claim set, the lane memo results and the outdoor pass's per-region records. Done means the full build finishes with node under 1 GB of heap and tools under 2.5 GB total.
由索引模型根据 Issue 内容生成。
描述
Part 2 of making the asset build finish on a 4 GB machine (part 1: #3421).
Observed. A per-second profile of the full asset build on 2026-11-14, at 15 jobs, shows the build's node process growing steadily: 98 MB at start, about 1.2 GB in the outdoor-world pass, and 2,017 MB at the claim audit, never falling back. Python peaked at about 800 MB in the later dungeon maps (fixed in #3421 by mapping Media.pk2).
Unknown, and it decides the fix. Either the build holds that much live data, or V8 is collecting lazily because its heap limit on a 16 GB machine is about 4 GB. On a 4 GB machine V8's limit is far lower, so in the first case the build fails with a heap out-of-memory error, and in the second it just runs more garbage collections.
Next steps.
- Run the full build at
SRO_BUILD_JOBS=2withNODE_OPTIONS=--max-old-space-size=1024under the per-second profiler.- If it finishes: the growth was lazy collection. Set an explicit heap ceiling from the memory budget in the build entry and close this issue.
- If it fails: take a heap snapshot at the claim audit and find the holder. The candidates are the publication ledger's claim set, the lane memo results kept for the whole run, and per-region records the outdoor pass keeps.
- Done when the full build finishes with node under 1 GB of heap and the tools under 2.5 GB in total.
- 主要语言
- Go
- 星标
- 97
- 派生
- 61
- 平均合并
- 4 小时 14 分钟
- 30 天内合并 PR
- 913
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
opensro-dev/opensro 的其他 Issue
-
area: client enhancement priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#3681 ·
维护者通常 1 天内回复
-
area: client bug priority: low
难度 2/5 1-3 小时 新手友好度 78/100
opensro-dev/opensro#3228 · 1 条评论 ·
维护者通常 1 天内回复
-
Format one minified client file with dprint (ongoing: one file per PR)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area: client enhancement good first issue priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#1 · 1 条评论 ·
维护者通常 1 天内回复
-
area: server bug priority: medium
难度 3/5 半天 新手友好度 55/100
opensro-dev/opensro#3687 ·
维护者通常 1 天内回复
-
area: ops bug priority: high
难度 4/5 3-5 天 新手友好度 32/100
opensro-dev/opensro#3685 ·
维护者通常 1 天内回复
查看 opensro-dev/opensro 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
unbound-force/gaze#353 ·
维护者通常 1 天内回复
-
bug cross-seed ready-for-human
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
OneBusAway/maglev#2102 ·
维护者通常 2 天内回复
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
维护者通常 1 天内回复