-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 BUG: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory #2279
Comments
Verified at https://github.com/danramteke/docker-astro-slow-build/runs/4643816143?check_suite_focus=true Is this the kind of issue that may be resolved behind our upcoming SSR flag, @matthewp? |
I'll have to take a look at the example but yes, most likely it is. |
Hey, this issue is out of date and may have been fixed in the latest version of Astro. If you can still reproduce the issue with the latest version of astro ( The latest static build process, used via |
@tony-sull @matthewp @jonathantneal looks like this is not resolved using Upgrade astro: https://github.com/danramteke/docker-astro-slow-build/runs/5219063956?check_suite_focus=true |
I encountered a memory issue, possibly due to Decap CMS. Before running npm run build, I manually deleted the dist folder, and everything worked perfectly. To automate this, I added the following configuration to my package.json:
|
What version of
astro
are you using?0.21.13
What package manager are you using?
yarn
What operating system are you using?
Mac
Describe the Bug
Small site renders fine on both my dev machines. When
astro build
runs as aRUN
step inside of a Docker build, it runs out of memory. Increasing the memory usingNODE_OPTIONS=--max_old_space_size=8192
still results in failureHere is the stack trace.
Link to Minimal Reproducible Example
https://github.com/danramteke/docker-astro-slow-build
The text was updated successfully, but these errors were encountered: