DEV Community

Fix of Angular-cli 'JavaScript heap out of memory' error while running 'ng serve'

Andrei Fedotov on January 17, 2019

First option: Run node command as: node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve where 8048 is new memory limit in m...

Read full post

Ivan Lysianok • Aug 19 '22

Thanks a lot :) First option worked for me.

SAFIR • Mar 8 '23

It worked for me too. Thanks @andreisfedotov

Naveen • Feb 11 '23

2023 angular 15 this solution works.
Thanks a lot :)

Scott Hardy • Nov 29 '19

I don't think this is correct and only a bandaid solution for local development. CircleCI and TraviisCI have memory limits for their containers. I know CircleCI is 4GB (at least in the most common tier). I also think giving 8Gbs of swap to nodeJS is not a good idea given developers will be running other memory heavy applications (IDE, Browser etc.. ) and most developers (if lucky) will have 16GBs of memory.

Sebastian Gutierrez • Jan 4 '24

Just to clarify, the max_old_space_size limit the amount of memory used for the process. So in CI environements (like BitBucket, Travis CI, etc) you can use this configuration to avoid use more than that. Instead of setting 8Gbs or 12Gb set ony the maximum your environment allows 4Gb for most common CI. This solved an issue with Angular after upgrating to version 14.

Samee Ullah • Oct 26 '21

Welldone, I just run this command in CMD "node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve" And it's work for me :-)

Hardik5Bavishi • Feb 6 '19

Thanks man!

2nd option helps me a lot.

It works now.

Sampath Lokuge • Nov 18 '19 • Edited

This helps me a lot. Thanks a lot!

i.e. 1st option worked for me.

Nilesh Sutar • Dec 6 '19

Thanks man, it helps me a lot...!

Wayne Fair • Jan 28 '20

You're a life-saver! Thanks!

kannanATexcelforte • May 6 '20

You are the master indeed !
Thanks a lot.

Jonathan Adamit • May 7 '20

Thanks!
Option #3: Set it as an environment variable.
SET NODE_OPTIONS=--max_old_space_size=8048

Andrei Fedotov • May 7 '20

Thanks for sharing! I added it into the note.

PritiMaurya • Dec 30 '19

Why this error is come ?
what is root couse of this error?

Andrei Fedotov • Jan 17 '20

The root of this problem lies in the insufficient amount of allocated memory for the application. This can happen when, for example, an application is quite large like an enterprise application. And there is not able to specify the heap allocation size with the help of ng command. However Node can be used not only to serve the application but also to perform such things like allocating more memory to the app.

J Sanjay • May 29 '24

Thank a ton! This woked for me