Build process memory growth from 98 MB to 2 GB

未关闭
#3,685 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
32/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
node.js
领域
build-system

调研方向

Read follow-up #3421 first for the earlier memory measurements, then locate the asset-pipeline build entry point that runs the claim audit and reproduces the growth. Run that build with a capped heap (for example node --max-old-space-size=...) and compare heap snapshots to tell retained data apart from lazy V8 GC under the 4 GB limit. Done when the source of growth is identified and either fixed or documented as a machine constraint.

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

描述

area: ops bug priority: high

Follow-up from #3421

The build's node process grows steadily, from 98 MB to 2 GB by the claim audit. Whether that is retained data or V8 collecting lazily under a 4 GB heap limit decides whether a 4 GB machine can finish. Needs a capped-heap run to diagnose.

Done when

  • Run the build with a capped heap to determine if growth is retained data or lazy GC
  • Identify the source of memory growth
  • Implement fix or document the constraint
主要语言
Go
星标
97
派生
61
平均合并
4 小时 14 分钟
30 天内合并 PR
913

环境准备

从这里开始

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

opensro-dev/opensro 的其他 Issue

查看 opensro-dev/opensro 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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