Skip to content

fix(ci): raise docs build heap limit to 8192MB to fix OOM#513

Merged
maloyan merged 1 commit into
mainfrom
fix/docs-build-oom
Jul 16, 2026
Merged

fix(ci): raise docs build heap limit to 8192MB to fix OOM#513
maloyan merged 1 commit into
mainfrom
fix/docs-build-oom

Conversation

@maloyan

@maloyan maloyan commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Summary

Docs deploy on main failed: https://github.com/maloyan/manim-web/actions/runs/29480765834

Docusaurus client and server compiled fine, then Node died during static site generation:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Process completed with exit code 134

Heap peaked at ~5.7GB against the existing 6144MB --max-old-space-size cap. The THREE namespace re-export (#510) grew the typedoc/SSG surface enough that the build now sits past the old limit (the last green run on f687ad8 was already at the edge).

Change

Bump NODE_OPTIONS: --max-old-space-size from 6144 to 8192 in both docs.yml and ci.yml docs-build steps. Runners have 16GB RAM, so this leaves comfortable headroom.

Testing

  • Config-only change; verification is the docs build job on this PR / next main push.

🤖 Generated with Claude Code

Docs build on main OOMed (exit 134) after Docusaurus client/server
compile, during SSG. Heap peaked at ~5.7GB against the 6144MB cap.
The THREE namespace re-export (#510) grew the typedoc surface enough
to push the build past the old limit. Runners have 16GB, so 8192 is
safe headroom.
@maloyan
maloyan merged commit 5281739 into main Jul 16, 2026
8 checks passed
@maloyan
maloyan deleted the fix/docs-build-oom branch July 16, 2026 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant