Angular 7/8 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

[arayik-yervandyan]

🐞 Bug report

Command (mark with an x)

- [ ] new
- [X] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description

With the last merge project build process is not working. I get failure that is pasted below.
Tried to change --max-old-space-size=4096 still not working.
Any suggestions what this can be ?

🔬 Minimal Reproduction

run command ng build --prod
in angular.json file we have

"production": {
	"optimization": true,
	"outputHashing": "all",
	"sourceMap": false,
	"extractCss": true,
	"namedChunks": false,
	"aot": true,
	"extractLicenses": true,
	"vendorChunk": false,
	"buildOptimizer": true,
	"fileReplacements": [
	{
		"replace": "src/environments/environment.ts",
		"with": "src/environments/environment.prod.ts"
	}
	]
},

🔥 Exception or Error

Here is the log file.

{ Error: Command failed: ng build --prod --configuration=config --output-path=test --base-href=/test/
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x8dbaa0 node::Abort() [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 2: 0x8dbaec  [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 3: 0xad83de v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 4: 0xad8614 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 5: 0xec5c42  [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 6: 0xec5d48 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 7: 0xed1e22 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 8: 0xed2754 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
 9: 0xed53c1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
10: 0xe9d636  [ng build --prod --configuration=config --output-path=test --base-href=/test/]
11: 0xeafee7 v8::internal::Factory::NewLoadHandler(int) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
12: 0xf2f4db v8::internal::LoadHandler::LoadFromPrototype(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::Smi>, v8::internal::MaybeHandle<v8::internal::Object>, v8::internal::MaybeHandle<v8::internal::Object>) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
13: 0xf36d1f v8::internal::LoadIC::ComputeHandler(v8::internal::LookupIterator*) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
14: 0xf3d94c v8::internal::LoadIC::UpdateCaches(v8::internal::LookupIterator*) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
15: 0xf3dffc v8::internal::LoadIC::Load(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Name>) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
16: 0xf42935 v8::internal::Runtime_LoadIC_Miss(int, v8::internal::Object**, v8::internal::Isolate*) [ng build --prod --configuration=config --output-path=test --base-href=/test/]
17: 0x235e3925be1d

🌍 Your Environment

Angular CLI: 7.3.1
Node: 10.15.1
OS: linux x64
Angular: 7.2.6
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.2
@angular-devkit/build-angular     0.13.2
@angular-devkit/build-optimizer   0.13.2
@angular-devkit/build-webpack     0.13.2
@angular-devkit/core              7.3.2
@angular-devkit/schematics        7.3.1
@angular/cdk                      7.3.3
@angular/cli                      7.3.1
@ngtools/webpack                  7.3.2
@schematics/angular               7.3.1
@schematics/update                0.13.1
rxjs                              6.4.0
typescript                        3.1.6
webpack                           4.29.0

[alan-agius4]

Hi, in the error stack trace, it seems that you are using a different configuration from "production", can you kindly share that configuration?

[arayik-yervandyan]

Sorry for mismatch here is configuration params that you need

"config": {
              "optimization": true,
              "outputHashing": "all",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": false,
              "aot": true,
              "extractLicenses": true,
              "vendorChunk": false,
              "buildOptimizer": true,
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.config.ts"
                }
              ]
            }

[nicobytes]

I have the same error:

My env:

[Bloodcast69]

Guys here's described the "workaround" for this problem: #5618

[mumairofficial]

• new
• build
• serve prod
• test
• e2e

I am facing same issue while ng serve --prod

Reference Image

[themanojshukla]

I to got the same error. NodeJs process uses around 1.5GB of RAM, and after few minutes of attempt to clean/allocate memory, it fails with error.

[themanojshukla]

UPDATE :-

I've seen this issue only on WINDOWS machine particularly. Anyone else, noticed that? Or have got same issue in other machines?

Note: I tried 2 Windows machine, all tests gave same result. Both machine have same config almost.
i.e. 8GB RAM/Admin Access For Bash/CMD/PowerShell/ i3 & i5 Processor (quad core, both).

And, I admit that the project that I'm working on is a MESS in terms of code quality.
I tried one clean code, full fledged application, ON WINDOWS, it was slower in build process, but worked fine.

I tried MESSY project's code, it never compile on default node heap allocation (around 1.2 GB, not sure.). It works if I allocate more heap memory to node process, say 5 GB. But, in that case too, it took more than 30 mins to build. I tried the 5 GB node heap option with and without --aot AND/OR --prod .

Same code when tried on CentOS could instance of 1GB RAM/ Virtual Xenon Processor (1 Core), generates build within 90 Seconds. with and without --aot AND/OR --prod

I'm not sure, but, looks like problem is with Node Service not with Angular CLI itself, coz I've seen some performance lag in new NodeJS releases after last update (locally on WINDOWS machine only).

Some observations below.:-

Even though allocating 5 GB of heap, it never used more than 1.9 GB (max) and allocation process was very slow.. it was increasing RAM consumption 1-2 MB per 3-5 seconds. And, was not using Disk Resource as it used to be in older version. (Disk access was very high previously on WINDOWS machine, but build process was faster without extra RAM allocation. This time, same machine almost same code with some bug fixes, but node was upgraded, disk consumption was lowered but slow build generation.)

Hope somebody can confirm this.

[tibinthomas]

Yes, I am also facing the same issue

[sswayney]

Same issue here running on a Mac book pro. macOs Mojoave. Any environment with production: true

[nokhodian]

same issue on ubuntu server 18.04, but this solved my problem:
node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng build --prod

[themanojshukla]

I've tried uninstalling Angular CLI 7, and installed 6.0.8. verified the downgraded version by ng version, still it breaks with the same error.

Maybe this could be because of nodeJs too. Coz, I'm building same code in CentOS 7, 1.75GB RAM (with 512MB swap memory), single core processor, and with angular CLI 7, it works there. It is breaking in my 2 windows machines.

For those, who can't afford allocating more RAM (due to less memory available) can create a SWAP memory from the space available from Hard Drive of system. It'll be little slower, but should work without System Upgrade. I've done the same. 👍

[j2L4e]

In my case the problem only appears, when building --prod --source-map. The normal --prod build runs just fine.

Using --max_old_space_size=8192 as suggested by @nokhodian it works with memory consumption peaking at ~3.8GiB during source map generation.

Build environment:

Angular CLI: 7.3.8
Node: 10.15.2
OS: linux x64
Angular: 7.2.12
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.10.4
@angular-devkit/build-angular     0.10.4
@angular-devkit/build-optimizer   0.10.4
@angular-devkit/build-webpack     0.10.4
@angular-devkit/core              7.0.4
@angular-devkit/schematics        7.1.0
@angular/cdk                      7.3.7
@angular/cli                      7.3.8
@angular/flex-layout              7.0.0-beta.19
@angular/material                 7.3.7
@angular/pwa                      0.11.0
@ngtools/webpack                  7.0.4
@schematics/angular               7.1.0
@schematics/update                0.13.8
rxjs                              6.4.0
typescript                        3.2.4
webpack                           4.19.1

[arayik-yervandyan]

In my angular.json file I have setted "sourceMap": false, but it doesn't helped me. Same issue for prod build

[ormico]

just chiming in here with same error message when running ng build when the build is working on a particular scss file

[geo242]

I also have this issue but can resolve it with "NODE_OPTIONS=--max-old-space-size=8192". Ram usage during build gets up about 14GB.

[ormico]

Same here. I found that after further searching. I've sent out instructions to our team to set this environment variable and set it on our build servers. Seems to work and build seems to be faster than before it stopped working.

[Calidus]

I started running into the same issue with Azure Pipelines: #https://github.com/Microsoft/azure-pipelines-image-generation/issues/854 I assumed it was a hosting problem, since don't have the issue on premise.

[j3gb3rt]

We are seeing this issue as well. With ng serve being the worse, but even normal ng build having issues now. Could this be sass related? Something seems off.

      "old_space": {
        "memorySize": 1280512000,
        "committedMemory": 1278567272,
        "capacity": 1155253856,
        "used": 1152333192,
        "available": 2920664
      },

Above is my old_space head info from the generated report. What could be making these numbers get so large?

[j3gb3rt]

Has anyone experienced this in a project that doesn't use sass?

[hvdscheer]

We are experiencing this problem when we use
ng build --prod
Sometimes needed because we use different environment settings.
node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng serve --prod solves the problem but the build time is exceeded to 3 minutes.
I don't think this issue is solved

[filipesilva]

This issue is the same as #5618 (comment), as far as I can tell.

I don't see a lot of things I can follow up and investigate though. @themanojshukla mentioned Windows was taking a lot longer. @j3gb3rt is asking about sass, and I have seen reports in the past about sass making things slower.

Does anyone have a reproduction that we can look at and try to debug?

[Calidus]

I have run into this issue on a project that does not use sass. I did some environment testing because I originally thought it was an issue relating to Azure Dev Ops.

Using Azure Dev Ops Pipelines:

• Hosted Linux agent with Node 10: Build succeeds
• Hosted Windows vs2017 Agent with Node 10: Build fails
• Hosted Windows vs2017 Agent with Node 6: Build fails
• Hosted Windows vs2019 Agent with Node 10: Build fails
• Hosted Windows vs2019 Agent with Node 6: Build fails
• Hosted Windows Container Agent with Node 10: Build Failed 5/10 attempts
• Install Build Agent on my dev machine(win10) with Node 10: Build Succeeds
• Install Build Agent on my dev machine(win10) with Node 6: Build Succeeds
• Dev machine(win10) using cmd with Node 10: Build Succeeds
• Dev machine(win10) using cmd with Node 6: Build Succeeds

[themanojshukla]

Yes @filipesilva and @Calidus my projects also don't use sass.

Let me give some more observations...

• The pet project (following best practices as much as can be) I created in around a year ago was working very fine that time ( I don't remember the CLI version I used). Now when I'm building it using --aot --prod it takes bit more time than before but never breaks. No sass used.
• New project (of course production code base & I admit, really really messy codes), it breaks on --aot --prod. No Sass used. Breaks on windows always. Sometimes works on ubuntu without allocating extra heap on node process, but success rate on ubuntu is 10% say.
• Another mid-level project (messy codes), works without extra heap allocation but takes a bit more time on both Windows & Ubuntu.
• Another pet project (following best practices as much as can be) works fine so far.. but very less files to compile, so can't be sure on processing loads.

When running ng build --aot --prod for the first time after machine start/restart. it takes 57seconds. afterwards, 22-25seconds only.

First Run Screenshot..

Second Run Screenshot..

Both are for same project.. and are of while writing this comment.

Hope it helps.

[noopur-dabhi]

I'm facing the same issue. Every time I build I get "JavaScript heap out of memory". I don't want to use node --max_old_space_size=8192 since this doesn't sounds best practice. Any other way to fix this?

[themanojshukla]

@noopur-dabhi I don't think it is fair to say that using node --max_old_space_size=8192 is not best practice.

It is nothing but allowing NODE process (which is going to build your app now) to use more than DEFAULT heap memory (from your RAM or SWAP area).

And this type of allocation is very very common in most of the app development (especially deployment) process. Example, in Java, if we want to restrict our java app heap usage, we add additional flag like --Xmx64m this means maximum heap memory allowed is 64MB.

So if 'Best Practice' is the only concern, I think it's not a problem using node --max_old_space=8192, this means you are allowing NODE process to use maximum of 8192MB from memory. nothing to do with Best Practice Concern.

[lcpautotester]

This is still crashing for me> any suggestions?
I tried "ng build --aot --prod"
and "node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng build --prod"

• Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
  92% chunk asset optimization TerserPlugin
  <--- Last few GCs --->

[9568:000002A08DC547B0] 183499 ms: Mark-sweep 1350.2 (1423.6) -> 1350.2 (1424.1) MB, 952.0 / 0.0 ms (average mu = 0.111, current mu = 0.000) allocation failure GC in old space requested
[9568:000002A08DC547B0] 184477 ms: Mark-sweep 1350.2 (1424.1) -> 1350.2 (1424.1) MB, 977.5 / 0.0 ms (average mu = 0.058, current mu = 0.000) last resort GC in old space requested

<--- JS stacktrace --->

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

0: ExitFrame [pc: 000001D7B1850481]

Security context: 0x008d8961d9b1
1: /* anonymous */ [0000006BEE99B319] [C:\CODE\V2\UX\node_modules\webpack-sources\node_modules\source-map\lib\source-node.js:~342] [pc=000001D7B3E70B48](this=0x01dae2403e31 ,0x0263a30a1241 <String[6]: "Mill">,0x030059303561 )
2: SourceNode_walk [000001779ECCDF31] [C:\CODE\V2\UX\node_modules\webpack-so...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Writing Node.js report to file: report.20190506.161503.9568.001.json
Node.js report completed
1: 00007FF775E1896A public: __cdecl v8::internal::GCIdleTimeHandler::GCIdleTimeHandler(void) __ptr64+4554
2: 00007FF775DC8956 uv_loop_fork+85542
3: 00007FF775DC941D uv_loop_fork+88301
4: 00007FF7761EE72E void __cdecl v8::internal::FatalProcessOutOfMemory(class v8::internal::Isolate * __ptr64,char const * __ptr64)+798
5: 00007FF7761EE667 void __cdecl v8::internal::FatalProcessOutOfMemory(class v8::internal::Isolate * __ptr64,char const * __ptr64)+599
6: 00007FF7762A2144 public: static bool __cdecl v8::internal::Heap::RootIsImmortalImmovable(int)+14068
7: 00007FF776297F52 public: bool __cdecl v8::internal::Heap::CollectGarbage(enum v8::internal::AllocationSpace,enum v8::internal::GarbageCollectionReason,enum v8::GCCallbackFlags) __ptr64+7234
8: 00007FF776296768 public: bool __cdecl v8::internal::Heap::CollectGarbage(enum v8::internal::AllocationSpace,enum v8::internal::GarbageCollectionReason,enum v8::GCCallbackFlags) __ptr64+1112
9: 00007FF776295C25 public: void __cdecl v8::internal::Heap::CollectAllGarbage(int,enum v8::internal::GarbageCollectionReason,enum v8::GCCallbackFlags) __ptr64+949
10: 00007FF7762A0174 public: static bool __cdecl v8::internal::Heap::RootIsImmortalImmovable(int)+5924
11: 00007FF7763D7E4D private: class v8::internal::HeapObject * __ptr64 __cdecl v8::internal::Factory::AllocateRawArray(int,enum v8::internal::PretenureFlag) __ptr64+61
12: 00007FF7763D87E2 private: class v8::internal::Handle __cdecl v8::internal::Factory::NewFixedArrayWithFiller(enum v8::internal::Heap::RootListIndex,int,class v8::internal::Object * __ptr64,enum v8::internal::PretenureFlag) __ptr64+66
13: 00007FF77641B0BA public: static class v8::internal::wasm::AsmType * __ptr64 __cdecl v8::internal::wasm::AsmType::Void(void)+69050
14: 00007FF776407A06 class v8::internal::MaybeHandle __cdecl v8::internal::BigIntLiteral(class v8::internal::Isolate * __ptr64,char const * __ptr64)+127094
15: 00007FF77649AFA0 public: static int __cdecl v8::internal::StoreBuffer::StoreBufferOverflow(class v8::internal::Isolate * __ptr64)+64256
16: 000001D7B1850481
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! Exit status 134
npm ERR!
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

[sefasenturk95]

I updated the node.js to the latest LTS (at this moment 12.13.0) version and everything work perfectly. No need anymore set the max-old-space-size.

This worked for me!

Updating to latest node.js worked for me too!

[MerySantos]

I updated the node.js to the latest LTS (at this moment 12.13.0) version and everything work perfectly. No need anymore set the max-old-space-size.

This worked for me!

[umairhafeez-r]

I updated the node.js to the latest LTS (at this moment 12.13.0) version and everything work perfectly. No need anymore set the max-old-space-size.

Worked for me too

[Disane87]

I updated the node.js to the latest LTS (at this moment 12.13.0) version and everything work perfectly. No need anymore set the max-old-space-size.

Worked for me too

I can confirm, that this is working.

[davidgg]

Same problem here. Angular 7. Any Node 12.X version.

Works with Node 10.

[MatricomHQ]

Upgrading to 12.x worked for me. Loving Angular less and less each day...

[umairhafeez-r]

Every release I recall a presentation at NGConfg by one of the angular members stating something like:

"We have over 400 applications at google and we dogfood angular before we release it into the wild. If any of the applications have to change in order to adapt the update, we don't release it"

I think every single release required some type of update to the code.

As far as I remember, they said that they test the applications to make sure nothing breaks after necessary code upgrades. I believe, upgrading the code to take in the enhancements is anyways inevitable.

But this current issue has nothing to do with that. It's more about application size. If the application size is growing, you will have to increase the heap size for the node process.

[rsivan]

Just happened to me after updating from 9.0.3 to 9.0.5

[rohithhasher]

Hi All..
I was using ubuntu 18.04 EC2 instance to build docker images.
This issue is resolved as soon as i change the instance type to t2.medium from t2.micro.

[tussharkhairnar]

I was facing same issue for ng serve,

npm cache clean --force resolve this issue

[error505]

NodeJS Update to latest version solved it for me.

[tussharkhairnar]

I have resolved by installing Nodejs V12 , I was facing issue with Nodejs V10

…

On Sat, 2 May 2020 at 01:59, Igor Iric ***@***.***> wrote: Node JS Update to latest version solved it for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13734 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH6IJ4PME7KZY3J7J3ARITDRPMWLXANCNFSM4GY5SKAQ> .

[filipesilva]

Heya all, this issue is pretty old by this point and we're mostly focused on resource usage issues on newer CLI version. This issue also contains several different problems that seem to manifest in similar ways, which makes it hard to zero-in on. If you're still seeing problems like this, please open a new issue with reproduction details.

[gayankasun]

use
"build:prod": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng build --configuration=prod", in your package.json file

this will tell node to exceed default memory allocation by given size in command.

[kyle-apex]

If it helps anyone else, when we switched from "@angular-devkit/build-angular": "0.803.26" to "@angular-devkit/build-angular": "0.803.27" it caused memory to run away during prod builds at ~43% build progress. It would get stuck at this step and escalate to >25GB of RAM rather than ~1.5GB.

When we switched back to "@angular-devkit/build-angular": "0.803.26", it worked again. 0.803.27 is a recent release around 6/11/20, so it would only explain new occurrences of this issue.

[Flyrell]

Seems like the issue is back with v10 release. Using @angular-devkit/build-angular v0.1000.0 and @angular/* packages v10.0.0.

Node: v14.1.0
NPM: 6.14.5

Stack trace:

<--- Last few GCs --->

[13013:0x108008000]  2808381 ms: Scavenge 2003.1 (2051.0) -> 2002.5 (2051.5) MB, 4.0 / 0.0 ms  (average mu = 0.117, current mu = 0.045) allocation failure 
[13013:0x108008000]  2809520 ms: Mark-sweep 2003.3 (2051.5) -> 2002.1 (2051.0) MB, 1132.9 / 0.0 ms  (average mu = 0.073, current mu = 0.026) allocation failure scavenge might not succeed
[13013:0x108008000]  2809535 ms: Scavenge 2003.1 (2051.0) -> 2002.5 (2051.5) MB, 3.3 / 0.0 ms  (average mu = 0.073, current mu = 0.026) allocation failure 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100bc569b node::Abort() (.cold.1) [/usr/local/bin/node]
 2: 0x1000816b5 node::FatalError(char const*, char const*) [/usr/local/bin/node]
 3: 0x10008181e node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
 4: 0x100180909 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 5: 0x1001808b3 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 6: 0x1002a0bfd v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 7: 0x1002a1f60 v8::internal::Heap::MarkCompactPrologue() [/usr/local/bin/node]
 8: 0x10029f947 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
 9: 0x10029e112 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
10: 0x1002a60d4 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
11: 0x1002a612a v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
12: 0x10028417d v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node]
13: 0x1004e7b16 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
14: 0x10074fe99 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/usr/local/bin/node]
zsh: abort      npm run start

After upgrading Node.js to v14.4.0 the issue seems to be resolved.

[arunmmanoharan]

@Flyrell I have the same issue with Nodejs 14.4.0 and Angular 10

[stingers]

@Flyrell I have the same issue with Nodejs 14.4.0 and Angular 10 but that not seems resolved

[Flyrell]

Yes, I was using the dev server for a little more today and the issue still exists.

[gvsakhil]

Yes the issue still exists with angular 10 and nodejs 12.16.1 :(

[superjulius]

@Flyrell @gvsakhil Avoid commenting on closed issues that are referring to old versions. There is an opened issue #16860 for NG9, which would be more appropriate.

Note that there is even now an issue #18087 for Angular 10, which got closed so you can expect some improvements with next release.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}