Angular API fatal error handler returned after process out of memory












1














I'm deploying angular 7 app to Azure, an error




API fatal error handler returned after process out of memory




is appear when run ng build --prod even in local system when running ng build --prod no error found except some warning



WARNING in Invalid background value at 9045:14. Ignoring.
WARNING in Invalid background value at 9064:14. Ignoring.
WARNING in Invalid background value at 9067:14. Ignoring.
WARNING in Invalid background value at 9070:14. Ignoring.
WARNING in Invalid background value at 9073:14. Ignoring.
WARNING in Invalid background value at 11642:14. Ignoring.



here is the log
Activity log



here is package.json



package.json



Thanks in advance!










share|improve this question
























  • What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
    – Walter Łuszczyk
    Nov 20 '18 at 11:12










  • it's "@angular-devkit/build-angular": "~0.10.0"
    – Kenana Reda
    Nov 20 '18 at 12:13










  • @WalterŁuszczyk I've added package.json kindly have alook
    – Kenana Reda
    Nov 20 '18 at 12:19
















1














I'm deploying angular 7 app to Azure, an error




API fatal error handler returned after process out of memory




is appear when run ng build --prod even in local system when running ng build --prod no error found except some warning



WARNING in Invalid background value at 9045:14. Ignoring.
WARNING in Invalid background value at 9064:14. Ignoring.
WARNING in Invalid background value at 9067:14. Ignoring.
WARNING in Invalid background value at 9070:14. Ignoring.
WARNING in Invalid background value at 9073:14. Ignoring.
WARNING in Invalid background value at 11642:14. Ignoring.



here is the log
Activity log



here is package.json



package.json



Thanks in advance!










share|improve this question
























  • What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
    – Walter Łuszczyk
    Nov 20 '18 at 11:12










  • it's "@angular-devkit/build-angular": "~0.10.0"
    – Kenana Reda
    Nov 20 '18 at 12:13










  • @WalterŁuszczyk I've added package.json kindly have alook
    – Kenana Reda
    Nov 20 '18 at 12:19














1












1








1







I'm deploying angular 7 app to Azure, an error




API fatal error handler returned after process out of memory




is appear when run ng build --prod even in local system when running ng build --prod no error found except some warning



WARNING in Invalid background value at 9045:14. Ignoring.
WARNING in Invalid background value at 9064:14. Ignoring.
WARNING in Invalid background value at 9067:14. Ignoring.
WARNING in Invalid background value at 9070:14. Ignoring.
WARNING in Invalid background value at 9073:14. Ignoring.
WARNING in Invalid background value at 11642:14. Ignoring.



here is the log
Activity log



here is package.json



package.json



Thanks in advance!










share|improve this question















I'm deploying angular 7 app to Azure, an error




API fatal error handler returned after process out of memory




is appear when run ng build --prod even in local system when running ng build --prod no error found except some warning



WARNING in Invalid background value at 9045:14. Ignoring.
WARNING in Invalid background value at 9064:14. Ignoring.
WARNING in Invalid background value at 9067:14. Ignoring.
WARNING in Invalid background value at 9070:14. Ignoring.
WARNING in Invalid background value at 9073:14. Ignoring.
WARNING in Invalid background value at 11642:14. Ignoring.



here is the log
Activity log



here is package.json



package.json



Thanks in advance!







node.js angular azure angular7 ng-build






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 29 '18 at 19:33









Goncalo Peres

1,3261318




1,3261318










asked Nov 20 '18 at 9:49









Kenana Reda

86




86












  • What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
    – Walter Łuszczyk
    Nov 20 '18 at 11:12










  • it's "@angular-devkit/build-angular": "~0.10.0"
    – Kenana Reda
    Nov 20 '18 at 12:13










  • @WalterŁuszczyk I've added package.json kindly have alook
    – Kenana Reda
    Nov 20 '18 at 12:19


















  • What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
    – Walter Łuszczyk
    Nov 20 '18 at 11:12










  • it's "@angular-devkit/build-angular": "~0.10.0"
    – Kenana Reda
    Nov 20 '18 at 12:13










  • @WalterŁuszczyk I've added package.json kindly have alook
    – Kenana Reda
    Nov 20 '18 at 12:19
















What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
– Walter Łuszczyk
Nov 20 '18 at 11:12




What version of @angular-devkit/build-angular package do you have in package.json, in the devDependencies?
– Walter Łuszczyk
Nov 20 '18 at 11:12












it's "@angular-devkit/build-angular": "~0.10.0"
– Kenana Reda
Nov 20 '18 at 12:13




it's "@angular-devkit/build-angular": "~0.10.0"
– Kenana Reda
Nov 20 '18 at 12:13












@WalterŁuszczyk I've added package.json kindly have alook
– Kenana Reda
Nov 20 '18 at 12:19




@WalterŁuszczyk I've added package.json kindly have alook
– Kenana Reda
Nov 20 '18 at 12:19












1 Answer
1






active

oldest

votes


















0














Looks like you need more gb memory to compile the project in wherever that ng build happens. Either increase memory, or do the ng build in your local, and commit the dist, then in Azure you just deploy with no build step.



ng build --prod --build-optimizer





share|improve this answer





















  • Thanks for answering! I've tried it and it still the same error
    – Kenana Reda
    Nov 20 '18 at 10:34










  • Increasing RAM has solved the problem
    – Kenana Reda
    Nov 21 '18 at 8:47











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390262%2fangular-api-fatal-error-handler-returned-after-process-out-of-memory%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Looks like you need more gb memory to compile the project in wherever that ng build happens. Either increase memory, or do the ng build in your local, and commit the dist, then in Azure you just deploy with no build step.



ng build --prod --build-optimizer





share|improve this answer





















  • Thanks for answering! I've tried it and it still the same error
    – Kenana Reda
    Nov 20 '18 at 10:34










  • Increasing RAM has solved the problem
    – Kenana Reda
    Nov 21 '18 at 8:47
















0














Looks like you need more gb memory to compile the project in wherever that ng build happens. Either increase memory, or do the ng build in your local, and commit the dist, then in Azure you just deploy with no build step.



ng build --prod --build-optimizer





share|improve this answer





















  • Thanks for answering! I've tried it and it still the same error
    – Kenana Reda
    Nov 20 '18 at 10:34










  • Increasing RAM has solved the problem
    – Kenana Reda
    Nov 21 '18 at 8:47














0












0








0






Looks like you need more gb memory to compile the project in wherever that ng build happens. Either increase memory, or do the ng build in your local, and commit the dist, then in Azure you just deploy with no build step.



ng build --prod --build-optimizer





share|improve this answer












Looks like you need more gb memory to compile the project in wherever that ng build happens. Either increase memory, or do the ng build in your local, and commit the dist, then in Azure you just deploy with no build step.



ng build --prod --build-optimizer






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 20 '18 at 10:12









freepowder

2796




2796












  • Thanks for answering! I've tried it and it still the same error
    – Kenana Reda
    Nov 20 '18 at 10:34










  • Increasing RAM has solved the problem
    – Kenana Reda
    Nov 21 '18 at 8:47


















  • Thanks for answering! I've tried it and it still the same error
    – Kenana Reda
    Nov 20 '18 at 10:34










  • Increasing RAM has solved the problem
    – Kenana Reda
    Nov 21 '18 at 8:47
















Thanks for answering! I've tried it and it still the same error
– Kenana Reda
Nov 20 '18 at 10:34




Thanks for answering! I've tried it and it still the same error
– Kenana Reda
Nov 20 '18 at 10:34












Increasing RAM has solved the problem
– Kenana Reda
Nov 21 '18 at 8:47




Increasing RAM has solved the problem
– Kenana Reda
Nov 21 '18 at 8:47


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390262%2fangular-api-fatal-error-handler-returned-after-process-out-of-memory%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy