Question
JavaScript heap out of memory while running a Nodejs app on App Platform
- Posted on August 20, 2021
- DigitalOcean App PlatformNode.js
Asked by Sri Charan Madhavapeddi
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
–
I ran into an issue with my latest build/deployment. I had a successful build locally on my machine. Can you help me on how to solve this?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Hello,
In app platform you only have 8gb of disk space + RAM. If either of those or both combined go over 8gb the build will fail with the out of memory errors you are seeing.
Yes we agree to your query but since the heap memory is sort of dynamic and increases during the runtime.
If this is a react or similar app you may need to add a memory limit to the build script something like and also refer to the below options.
react-scripts --max_old_space_size=2048 build
You may need to add 2 environment variables with BUILD_SCOPE:
Key: NODE_OPTIONS Value: --max-old-space-size=4096
Key: GENERATE_SOURCEMAP Value: false
Hope this helps!
Cheers, Sri Charan
Appreciate this question is a little old but ran into the same issue, and this post comes up when searched.
I fixed this by adding the following as an Environment Variable within the relevant App service settings.
This was a sufficient increase for my build to work.
Hope this helps someone else experiencing failed builds.