Out of memory with npm run build

Question

I have a react project, about 40MB. I run 'npm run build' with the param --max-old-space-size=4096.

At my local, about 8GB RAM, the build is running fine. But on Jenkins (AWS EC2 hosted one, t2.medium) 4GB, either 'Out Of Memory' or crash EC2 instance.

Please advice if any way we can overcome on Jenkins 4GB RAM.

Thanks,

score 1 · Answer 1 · answered May 20 '20 at 18:51

You should also check if there aren't any other apps eating out the memory on that EC2 instance. Because the react build itself, consuming 4 GB of memory, in a small project, is much unlikely to happen!

This thread might help you: How to monitor EC2 instances by memory?

score 0 · Answer 2 · answered May 20 '20 at 18:20

0

You need an instance with more memory, it's as simple as that. A t2.medium has 4GB total memory, but of course the system needs some of it for other processes also.

answered May 20 '20 at 18:20

ruohola

21,987
6
62
97

Thank you but the original question is do we have any way to still control memory of npm and maybe trade off performance. I don't have the option for now to increase instance type because of 'budget' constraints. – Nghia Do May 20 '20 at 19:52
Don't pass the --max-old-space-size flag? – ruohola May 20 '20 at 19:56
Do not pass, it throws Out Of Memory – Nghia Do May 20 '20 at 22:54
Try to pass something like 2048 to the flag. The default is 512MB, so it needs more, but maybe not the whole 4GB. – ruohola May 21 '20 at 06:31
I have tried that one too, 2048 ends up the same result. – Nghia Do May 21 '20 at 09:44
So my answer is your only solution then. – ruohola May 21 '20 at 10:46

Out of memory with npm run build

2 Answers2