Angular Production Build is taking about 1.5 GB of memory and still runs Out Of Memory

Question

Angular2 cli Project Production Build [ng build -prod] getting struck on 92% and getting error message like, running out of heap memory. Is there any solution for it? Project consists of huge number of components. Normal build is working fine [ng build]

Screenshot

Thank you

`--max_old_space_size` https://github.com/angular/angular-cli/issues/7024 — yurzui, Aug 03 '17 at 05:27
Thank you, already tried same command but it doesn't work for me. — Roshin Thomas, Aug 03 '17 at 05:31
try with : node --max_old_space_size=4096 node_modules/webpack/bin/webpack.js — Sandip - Frontend Developer, Aug 03 '17 at 05:32
@SandipPatel getting error : No configuration file found and no output filename configured via CLI option. A configuration file could be named 'webpack.config.js' in the current directory. Use --help to display the CLI options. — Roshin Thomas, Aug 03 '17 at 05:41
@yurzui : ng build -prod -aot=false this command will work, but setting flag "false" and running is not a good solution i think, because it will escape template errors — Roshin Thomas, Aug 03 '17 at 05:43
I know that `-aot=false` will work for you but try adding `--max_old_space_size` to `ng.cmd` command — yurzui, Aug 03 '17 at 05:44
@yurzui : but how to set --max_old_space_size, where i can find ng.cmd — Roshin Thomas, Aug 03 '17 at 05:46
it's sad that we have such problems with building big applications — yurzui, Aug 03 '17 at 05:54
@yurzui : that's correct, angular 2 need to find solution for it. — Roshin Thomas, Aug 03 '17 at 06:08

score 3 · Answer 1 · answered Aug 03 '17 at 05:59

3

There is only one workaround today.

Open ./node_modules/.bin/ng.cmd and add --max_old_space_size option

@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe" --max_old_space_size=8192 "%~dp0\..\@angular\cli\bin\ng" %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node  --max_old_space_size=8192  "%~dp0\..\@angular\cli\bin\ng" %*
)

Or you can upgrade your computer:)

Related issue on github

https://github.com/angular/angular-cli/issues/5618

answered Aug 03 '17 at 05:59

yurzui

205,937
32
433
399

1

Thanks yurzui, but node_modules folder is dynamically creating file na? when we run npm install, setting "max_old_space_size" may work in our system, but many people work together, this cant be solve using setting memory size on each machine? is there any quick solution to add it in package.json file? so it will run and execute on all machines. – Roshin Thomas Aug 03 '17 at 06:12
running on 8 GB RAM :) – Roshin Thomas Aug 03 '17 at 06:14

score 0 · Answer 2 · answered Jun 16 '21 at 07:52

If you are working with a Node Version >= 8, you can use the solution posted in Node.js heap out of memory:

In your package.json file, replace ng build xxx with node --max_old_space_size=8192 ./node_modules/@angular/cli/bin/ng build xxx

The value 8192 is the space in MB which node and angular as well will be allowed to use

Aswin KV · Answer 3 · 2017-08-03T09:14:51.430

-1

Please check the version of Angular CLI, If its 1.2.6 downgrade it to 1.2.1. It will work. I too have the same issue and solved by this mean. NB: it's only a temporary fix. Hope cli team will solve the issue ASAP.

edited Aug 03 '17 at 09:14

answered Aug 03 '17 at 09:08

Aswin KV

1,710
2
12
23

Getting error like : ERROR in ./src/main.ts Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in 'D:\projectpath\src' @ ./src/main.ts 3:0-74 @ multi ./src/main.ts – Roshin Thomas Aug 04 '17 at 05:14

Angular Production Build is taking about 1.5 GB of memory and still runs Out Of Memory

3 Answers3