Raise Node heap for release builds (macOS OOM) - #5
Merged
Conversation
vite build died with "JavaScript heap out of memory" on both macOS runners (7GB RAM, default Node heap cap) now that the bundle includes Monaco. Give the build step a 4GB old-space limit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
mohnjiles
enabled auto-merge
July 25, 2026 05:25
ionite34
approved these changes
Jul 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The v0.3.0 tag build failed on both macOS targets:
vite build(the tauri-actionbeforeBuildCommand) was killed with "FATAL ERROR: Ineffective mark-compacts near heap limit — JavaScript heap out of memory". The macOS runners have the least memory (7GB on ARM), and the bundle now includes Monaco, which blows past Node's default old-space cap during the rollup pass. Linux succeeded; this setsNODE_OPTIONS: --max-old-space-size=4096on the build step so all platforms build reliably.After merging, I'll delete and re-push the
v0.3.0tag so the release rebuilds from a commit containing this fix.Test plan
🤖 Generated with Claude Code