Asset build: the build process's heap grows to 2 GB

オープン
#3,422 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go, javascript, nodejs, python

調査の方向性

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 の本文から書いたものです。

説明

area: client bug priority: critical

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.

  1. Run the full build at SRO_BUILD_JOBS=2 with NODE_OPTIONS=--max-old-space-size=1024 under 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.
  2. 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分
マージ済み PR(30日)
913

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

opensro-dev/opensro のほかの issue

opensro-dev/opensro の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。