Skip to content

fix(release): raise Node heap to avoid macOS build OOM#41

Merged
Ron537 merged 1 commit intomainfrom
fix/mac-build-oom
May 7, 2026
Merged

fix(release): raise Node heap to avoid macOS build OOM#41
Ron537 merged 1 commit intomainfrom
fix/mac-build-oom

Conversation

@Ron537
Copy link
Copy Markdown
Owner

@Ron537 Ron537 commented May 7, 2026

Problem

Release run 25514990847 for v0.11.2 failed on macos-latest during electron-vite build:

FATAL ERROR: Ineffective mark-compacts near heap limit
Allocation failed - JavaScript heap out of memory
sh: line 1:  7442 Abort trap: 6           electron-vite build
##[error]Process completed with exit code 134.

Renderer bundle includes the Monaco editor chunk (~6 MB) and Vite 7 keeps a larger in-memory graph than v6, so the build now exceeds Node's default 2 GB old-space heap on the macOS runner. Linux + Windows happened to squeak under the limit but the same risk applies to them.

Fix

Set NODE_OPTIONS=--max-old-space-size=8192 at the build job level. 8 GB is comfortably under the macos-latest runner's 14 GB, and applies uniformly to all three platforms.

Next step

Once merged, re-cut the v0.11.2 tag (or push a v0.11.3) so the macOS .dmg actually publishes.

The v0.11.2 release run (25514990847) failed on macos-latest with
"FATAL ERROR: Ineffective mark-compacts near heap limit Allocation
failed - JavaScript heap out of memory" while electron-vite was
bundling the renderer. The Monaco editor chunk (~6 MB) plus Vite 7's
larger in-memory graph push past Node's default 2 GB limit on the
macOS runner.

Set NODE_OPTIONS=--max-old-space-size=8192 at the job level so all
three platforms run with the same heap cap. 8 GB is comfortably
under the macos-latest runner's 14 GB and matches what other
Electron/Monaco projects use.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Ron537 Ron537 merged commit baed4a1 into main May 7, 2026
5 checks passed
@Ron537 Ron537 deleted the fix/mac-build-oom branch May 7, 2026 18:46
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