Asset build: the build process's heap grows to 2 GB
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, javascript, nodejs, python
- Domain
- performance, tooling
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Go
- Stars
- 97
- Forks
- 61
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 913
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opensro-dev/opensro
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
area: client bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensro-dev/opensro#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Format one minified client file with dprint (ongoing: one file per PR)Possibly taken A pull request linked to this issue is open or already merged. Openarea: client enhancement good first issue priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#1 · 1 comment ·
Maintainers usually reply within 1 day
-
area: server bug priority: medium
Difficulty 3/5 Half a day Newbie friendliness 55/100
opensro-dev/opensro#3687 ·
Maintainers usually reply within 1 day
-
area: ops bug priority: high
Difficulty 4/5 3-5 days Newbie friendliness 32/100
opensro-dev/opensro#3685 ·
Maintainers usually reply within 1 day
All issues in opensro-dev/opensro
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Maintainers usually reply within 1 day