Building Angular project lead to heap out of memory

Question

When trying to build an Angular project on a Linux server with -aot flag, I get an error. I tried upgrading my instance to a higher CPU core, more RAM and turn on a SWAP partition but still the error just occur faster.

Here's while trying to build from terminal along with the command with the flags I use.

ng build --target=production --environment=prod --aot
Your global Angular CLI version (1.7.2) is greater than your local
version (1.4.7). The local Angular CLI version is used.

To disable this warning use "ng set --global warnings.versionMismatch=false".
 10% building modules 5/5 modules 0 activeTemplate parse warnings:                 
The <template> element is deprecated. Use <ng-template> instead ("
[WARNING ->]<template [ngIf]="!isClosed">
  <div [class]="'alert alert-' + type" role="alert" [ngClass]="classes""): ng:///****************node_modules/ngx-bootstrap/alert/alert.component.d.ts.AlertComponent.html@1:0
 92% chunk asset optimization                                                             
<--- Last few GCs --->

  133611 ms: Mark-sweep 1302.6 (1435.2) -> 1297.8 (1435.2) MB, 1112.6 / 0.0 ms [allocation failure] [GC in old space requested].
  134724 ms: Mark-sweep 1297.8 (1435.2) -> 1297.7 (1435.2) MB, 1112.7 / 0.0 ms [allocation failure] [GC in old space requested].
  135854 ms: Mark-sweep 1297.7 (1435.2) -> 1302.7 (1406.2) MB, 1129.8 / 0.0 ms [last resort gc].
  136983 ms: Mark-sweep 1302.7 (1406.2) -> 1307.9 (1406.2) MB, 1128.8 / 0.0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0xb8bacacfb39 <JS Object>
    1: find_variable [0xb8baca04381 <undefined>:~3539] [pc=0xbdb4151ee32] (this=0xa9144042161 <an AST_Function with map 0xd6ccb950f99>,name=0x1f852792bb29 <String[12]: DOMException>)
    2: visit [0xb8baca04381 <undefined>:3449] [pc=0xbdb4151d969] (this=0x3da6d780b621 <a TreeWalker with map 0xd6ccb9394c9>,node=0x2f9919fb8e91 <an AST_SymbolRef with map 0xd6ccb9628c9>,descend=0x2e68ca83edd1 <JS Fu...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [ng]
 2: 0x109bf8c [ng]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [ng]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [ng]
 5: v8::internal::Factory::NewInternalizedStringImpl(v8::internal::Handle<v8::internal::String>, int, unsigned int) [ng]
 6: v8::internal::StringTable::LookupString(v8::internal::Isolate*, v8::internal::Handle<v8::internal::String>) [ng]
 7: v8::internal::LookupIterator::PropertyOrElement(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, bool*, v8::internal::LookupIterator::Configuration) [ng]
 8: v8::internal::Runtime::GetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>) [ng]
 9: 0xed3501 [ng]
10: v8::internal::Runtime_KeyedGetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [ng]
11: 0xbdb262092a7
Aborted (core dumped)

I tried the solution mentioned here, https://www.npmjs.com/package/increase-memory-limit But still with no luck

Shardul · Accepted Answer · 2018-07-18 19:07:19Z

6

For prod build, run following command:

node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build --target production

For more optimization flags, below command:

It has inbuilt cache busting and other goodies:

node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build --target production --build-optimizer --vendor-chunk

answered Jul 18, 2018 at 19:07

Shardul

1,0121 gold badge13 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

user2280167 Over a year ago

Just out of curiosity, it has to be used in same syntax you wrote. Can't use ng build directly, as I used above?

Ramil Aliyev 007 Over a year ago

It is not working for me. My PC RAM is 16 gb and 11gb is free

Vaibhav · Accepted Answer · 2018-07-18 19:02:20Z

1

try running

node --max-old-space-size=8192

where 8192 is size in MB

answered Jul 18, 2018 at 19:02

Vaibhav

1,50713 silver badges17 bronze badges

1 Comment

user2280167 Over a year ago

And when should I try ng build? After I run that?

RandomUser · Accepted Answer · 2019-06-04 14:57:47Z

1

As Filipe Silva recommends in the angular-cli repository, add a new entry in the scripts section of your package.json file:

"ng-high-memory": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng",

and use it this way:

npm run ng-high-memory --

You have to remember to use the double dash before the arguments, otherwise they might not be parsed correctly:

npm run ng-high-memory -- serve

answered Jun 4, 2019 at 14:57

RandomUser

1,2441 gold badge13 silver badges26 bronze badges

Comments

amritashan · Accepted Answer · 2018-07-18 19:16:00Z

0

This does not look like a hardware limitation problem as such which can be resolved by upgrading the memory or processor. I once had a build running out of memory, but it turned out that there was a circular reference where a source file A required a source file B and then B also required A. It was a code design issue, of course.

I would suggest you to try a simple build first and check to see if it goes well.

ng build

Also, the Angular doc mentions that when using ng build --prod, (not --target=production), it performs an AOT compilation, among other things:

https://angular.io/guide/deployment

The --prod meta-flag engages the following optimization features.

Ahead-of-Time (AOT) Compilation: pre-compiles Angular component templates.

Production mode: deploys the production environment which enables production mode.

You might want to install the latest version of the Angular CLI and see if that helps.

answered Jul 18, 2018 at 19:16

amritashan

5834 silver badges21 bronze badges

2 Comments

user2280167 Over a year ago

It works fine if not ahead of compilation to problem, the problem happens only when using the -aot flag.

amritashan Over a year ago

Did you try using just the ng build --prod command. As I have mentioned above, the doc states that this will do a AOT compilation also. It does everything that is required for production mode, so you need not use any other flags.

Ramil Aliyev 007 · Accepted Answer · 2021-05-30 10:11:00Z

0

I faced same issue on Angular 4 project. The problem is my Node Js version is not compatible Angular 4, I installed Node Js v6.17.1 and problem resolved for me.

For more details Angular and Node Js compatibility you can visit this link : Is there a compatibility list for Angular / Angular-CLI and Node.js?

answered May 30, 2021 at 10:11

Ramil Aliyev 007

5,6102 gold badges38 silver badges59 bronze badges

Collectives™ on Stack Overflow

Building Angular project lead to heap out of memory

5 Answers 5

2 Comments

1 Comment

Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

2 Comments

1 Comment

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related