Version 9: performance issues & out of memory errors

[filipesilva]

If you are experiencing performance problems or out of memory errors with Angular CLI version 9, please let us known on this issue.

[alialtun14]

ng build -c mhsb

10% building 3/3 modules 0 active
<--- Last few GCs --->

[11664:000001BF4FF4BB60]    82832 ms: Mark-sweep 1372.0 (1455.8) -> 1363.3 (1456.3) MB, 1956.2 / 0.0 ms  (average mu = 0.156, current mu = 0.088) allocation failure scavenge might not succeed      
[11664:000001BF4FF4BB60]    84892 ms: Mark-sweep 1367.8 (1456.3) -> 1365.2 (1456.3) MB, 1955.4 / 0.0 ms  (average mu = 0.105, current mu = 0.051) allocation failure GC in old space requested      


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 000001F0724DC5C1]
    1: StubFrame [pc: 000001F0725040B1]
Security context: 0x0308fb49e6e9 <JSObject>
    2: onSubstituteNode(aka onSubstituteNode) [00000211020875B9] [D:\QLASS\node_modules\typescript\lib\typescript.js:76870] [bytecode=00000000D32B6A19 offset=0](this=0x0323baa826f1 <undefined>,hint=1,node=0x00d01b8a95b9 <IdentifierObject map = 0000034C8ACA3939>)
    3: onSubstituteNode(aka onSubstituteNode) [00000211...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7B607DD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
 2: 00007FF7B6058886 node::MakeCallback+4534
 3: 00007FF7B6059200 node_module_register+2032
 4: 00007FF7B63730DE v8::internal::FatalProcessOutOfMemory+846
 5: 00007FF7B637300F v8::internal::FatalProcessOutOfMemory+639
 6: 00007FF7B6559804 v8::internal::Heap::MaxHeapGrowingFactor+9620
 7: 00007FF7B65507E6 v8::internal::ScavengeJob::operator=+24550
 8: 00007FF7B654EE3C v8::internal::ScavengeJob::operator=+17980
 9: 00007FF7B6557B87 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF7B6557C06 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF7B66872B0 v8::internal::Factory::NewByteArray+112
12: 00007FF7B6AC583C v8::internal::compiler::MachineOperatorReducer::ReduceFloat64RoundDown+7564
13: 00007FF7B6901230 v8::internal::compiler::Pipeline::AllocateRegistersForTesting+4608
14: 00007FF7B68F95DB v8::internal::compiler::ValueNumberingReducer::operator=+10107
15: 00007FF7B653362A v8::internal::Zone::NewExpand+3034
16: 00007FF7B6535C44 v8::internal::Zone::NewExpand+12788
17: 00007FF7B65883B9 v8::internal::OptimizingCompileDispatcher::InstallOptimizedFunctions+393
18: 00007FF7B642DE23 v8::internal::StackGuard::HandleInterrupts+531
19: 00007FF7B66FEAB7 v8::internal::operator<<+71991
20: 000001F0724DC5C1

[alialtun14]

We solve this problem (when compile with ng build -c mhsb) we use following command.

.\ngs.cmd build -c mhsb

ngs.cmd: @node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng %1 %2 %3 %4 %5

When we use this command, when the compile process reaches 92% after 10 minutes, it encounters the error below.

92% chunk asset optimization TerserPluginFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 00007FF7B607DD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
 2: 00007FF7B6058886 node::MakeCallback+4534
 3: 00007FF7B6059200 node_module_register+2032
 4: 00007FF7B63730DE v8::internal::FatalProcessOutOfMemory+846
 5: 00007FF7B637300F v8::internal::FatalProcessOutOfMemory+639
 6: 00007FF7B6559804 v8::internal::Heap::MaxHeapGrowingFactor+9620
 7: 00007FF7B6557CCB v8::internal::Heap::MaxHeapGrowingFactor+2651
 8: 00007FF7B6681B2B v8::internal::Factory::AllocateRawWithImmortalMap+59  
 9: 00007FF7B66845DD v8::internal::Factory::NewRawTwoByteString+77
10: 00007FF7B6750270 v8::internal::LookupIterator::Start<1>+32464
11: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
12: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
13: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
14: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
15: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
16: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
17: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
18: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
19: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
20: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
21: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
22: 00007FF7B675065F v8::internal::LookupIterator::Start<1>+33471
23: 00007FF7B674FF07 v8::internal::LookupIterator::Start<1>+31591
24: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
25: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
26: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
27: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
28: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
29: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
30: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
31: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
32: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
33: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
34: 00007FF7B674FF3C v8::internal::LookupIterator::Start<1>+31644
35: 00007FF7B674BD62 v8::internal::LookupIterator::Start<1>+14786
36: 00007FF7B674CAD5 v8::internal::LookupIterator::Start<1>+18229
37: 00007FF7B674EE7B v8::internal::LookupIterator::Start<1>+27355
38: 00007FF7B674CB60 v8::internal::LookupIterator::Start<1>+18368
39: 00007FF7B674EE7B v8::internal::LookupIterator::Start<1>+27355
40: 00007FF7B674CB60 v8::internal::LookupIterator::Start<1>+18368
41: 00007FF7B674B77D v8::internal::LookupIterator::Start<1>+13277
42: 00007FF7B63A13FC v8::internal::DeferredHandles::Iterate+1116
43: 00007FF7B6743736 v8::internal::WasmJs::Install+230838
44: 00007FF7B674365B v8::internal::WasmJs::Install+230619
45: 0000014B2DCDC721
# Fatal error in , line 0
# API fatal error handler returned after process out of memory on the background thread
#FailureMessage Object: 000000A352EFA150^CTerminate batch job (Y/N)? y

[filipesilva]

@alialtun14 are you seeing this with version 9 now, and did it not happen with version 8?

I'd like to take a look at the project if possible. Giving me access to a new private github repository is a good way of doing this for private projects.

[alialtun14]

We have taken same error when we used "ng build -c mhsb". We have solved this problen i V8 by using max_old_space_size=8192. Today after upgrading to V9 and compile with max_old_space_size=8192 we started the error again.

[alialtun14]

I'd like to take a look at the project if possible. Giving me access to a new private github repository is a good way of doing this for private projects.

Our project is in gitlab reposiyory. If you share your email adrese with alialtun14@gmail.com. I can share zip file of our project.

[4zriel]

Hi - error in private company repo:
What could You help:

• newest cli, and all ng.
• when targeting es5 all works fine,
• when target is es2015 , build ends with stackoverflow :/
• optimalization false helps but this is not a solution :/

WARNING in Terser Plugin: Condition always false [vendor-es2015.89fba3b2bb0ffec12a97.js:181165,4]

WARNING in Terser Plugin: Dropping unreachable code [vendor-es2015.89fba3b2bb0ffec12a97.js:181165,11]

...

WARNING in Terser Plugin: Condition always false [vendor-es2015.89fba3b2bb0ffec12a97.js:39575,8]

WARNING in Terser Plugin: Condition left of || always false [vendor-es2015.89fba3b2bb0ffec12a97.js:61851,19]

WARNING in Terser Plugin: Condition left of || always false [vendor-es2015.89fba3b2bb0ffec12a97.js:61853,23]

WARNING in Terser Plugin: Dropping side-effect-free statement [vendor-es2015.89fba3b2bb0ffec12a97.js:209626,16]

ERROR in main-es2015.d92b662609fbc64cbd74.js from Terser
RangeError: Maximum call stack size exceeded
    at Array.push (<anonymous>)
    at Tn.push (C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:76200)
    at AST_SymbolDefClass.transform (C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:79125)
    at C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:82505
    at AST_ClassExpression.transform (C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:79182)
    at C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:81712
    at AST_Dot.transform (C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:79182)
    at C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:81532
    at AST_Call.transform (C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:79182)
    at C:\source\DEV\MAIN\WebNg8\node_modules\terser\dist\bundle.min.js:1:81712

ps. dont suggest by dir nam - it is ng9 ;)

[filipesilva]

@4zriel I edited your comment to remove a large chunk of terser warnings in the log that I reviewed and know is not relevant to the problem at hand. I removed it because it was very long and made it hard to read the rest of this issue thread.

[filipesilva]

@alialtun14 I just tried building with the increased memory and it seemed to build fine:

kamik@RED-X1C6 MINGW64 /d/sandbox/QLASS.V8
$ node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng build -c mhsb

chunk {0} runtime.a8ef3a8272419c2e2c66.js (runtime) 1.45 kB [entry] [rendered]
chunk {1} main.742b09869a13ccbb2f64.js (main) 11.4 MB [initial] [rendered]
chunk {2} polyfills.f5b379c03ee1455b2258.js (polyfills) 45.5 kB [initial] [rendered]
chunk {3} styles.b7204deb7fc86e3c9129.css (styles) 21.5 kB [initial] [rendered]
chunk {4} vendor.8fa60aebff14da44025f.js (vendor) 980 kB [initial] [rendered]
chunk {scripts} scripts.f7e72443ce1ee0185d9e.js (scripts) 229 kB [entry] [rendered]
Date: 2020-02-07T15:13:56.679Z - Hash: fdccd0547616a05c53dd - Time: 905229ms

What version of node are you on? There were a couple of node versions that had memory problems. I am on Node v12.4.0.

@4zriel what version of node are you on as well? Can you try the one I mentioned above, or perhaps considering sharing the project privately with me?

[4zriel]

@filipesilva
I'll love to share but then I'll propalby need to look for another work ;)
I'm using node 13.3.0, and I tried 1st this trick with inceased memory (I set sth about 10k maybe it is too much...) but it didn't change anything...As i said - ng serve and ng buil (without --prod so without --optimization works perfectly fine). It is quite big monorepo, with a lot of iternal lib, but ng update worked surpriselgly well :)

[filipesilva]

@4zriel since you have a monorepo, I think you might be suffering from case 2 in https://angular.io/guide/ivy-compatibility#payload-size-debugging. Can you try the approach described in #16799 (comment) and see if it works please?

To be clear, the approach is to add "sideEffects": false to the package.json of shared libraries. If the library doesn't actually have a package.json, you can add one with just {"sideEffects": false}.