FATAL ERROR: Committing semi space failed. Allocation failed

[gayankasun]

My project got build failed in Devops. But its succssfully got build in my pc with same command
any reason for that?

Command : node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng build --
configuration=prod
Angular version : 9.1.7
Node version :v12.17.0

[AndrewKushnir]

Hi @gayankasun, it looks like similar issues are also reported in angular/angular-cli#16860, so I'm transferring this ticket to the Angular CLI repo for further investigation. Thank you.

[alan-agius4]

This is actually caused by NGCC, so back to the FW 😀

[JoostK]

I'm afraid we can't diagnose the cause of this issue without being able to reproduce ourselves. You can try running ngcc manually instead of using the CLI using:

node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ngcc --properties browser module main --first-only --create-ivy-entry-points

Alternatively/additionally, you could try passing the --trace_gc flag to node to get far more insight into the behavior of the garbage collector.

[jjmarty]

I was also running into this issue in Azure Devops pipelines which started around the same timeframe on 6/10/2020. I resolved my issue by committing package-lock.json.

I believe my particular issue was caused by the build agent installing a slightly different npm dependency version on one or more packages. I believe package-lock.json file fixed it by installing the exact same dependencies on the azure build agent that I have locally on my machine.

Most likely an issue with the version of "@angular-devkit/build-angular".

[gayankasun]

I have found the reason for it. its because of latest angular cli version. its working fine with angular/cli = 9.1.6",

[JoostK]

Based on the comments and the investigation I did for angular/angular-cli#18087, I'm pretty certain this has the same cause. See angular/angular-cli#18087 (comment) for details. CLI 9.1.10 and 10.0.1 contain the fix.

[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.}