blocks|key|4573816|text|如果你看一下源代码：github/v8，似乎你试图保留一个非常大的object.According给我的经验如果你试图解析一个巨大的JSON对象，但当我尝试用JSON和node0.11.13解析你的输出时，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4573817|你不需要更多的--stack-size，你需要更多的内存：--max_new_space_size和/或--max_old_space_size。|style|CODE|4573818|除此之外，我能给您的唯一提示是尝试另一个JSON解析器和/或尝试将输入格式更改为JSON行而不是仅JSON。|4573819|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/v8/v8-git-mirror/blob/master/src/heap/heap-inl.h^0|A|9|0|0|7|C|T|K|1G|K|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]|$A|Y|B|Z|F|G]|$A|10|B|11|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

If you have a look at the source: <a href="https://github.com/v8/v8-git-mirror/blob/master/src/heap/heap-inl.h" rel="noreferrer">github/v8</a>, it seems that you try to reserve a very big object.According to my experience it happens if you try to parse a huge JSON object, but when I try to parse your output with JSON and node0.11.13, it just works fine.

You don't need more <code>--stack-size</code>, you need more memory: <code>--max_new_space_size</code> and/or <code>--max_old_space_size</code>.

The only hint I can give you beside that is trying another JSON-parser and/or try to change the input format to JSON line instead of JSON only.

blocks|key|4573900|text|要解决此问题，您需要通过使用选项--max_old_space_size增加内存限制来运行应用程序。默认情况下，Node.js的内存限制为512MB。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4573901|node+--max_old_space_size=2000++server.js+|code-block|syntax|javascript|4573902|entityMap^0|G|K|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

To solve this issue you need to run your application by increasing the memory limit by using the option <code>--max_old_space_size</code>. By default the memory limit of Node.js is 512 mb.

<pre><code>node --max_old_space_size=2000 server.js 
</code></pre>

blocks|key|67441|text|我发现在Node4.1.1中max_new_space_size不是一个选项，单独使用max_old_space_size并不能解决我的问题。我将以下内容添加到我的shebang中，并且这些内容的组合似乎可以工作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|67442|#!/usr/bin/env+node+--max_old_space_size=4096+--optimize_for_size+--max_executable_size=4096+--stack_size=4096|code-block|syntax|javascript|67443|编辑:+4096+===+4+4GB内存，如果您的设备内存不足，您可能希望选择较小的内存。|67444|更新:在运行grunt时也发现了这个错误，之前是这样运行的：|67445|./node_modules/.bin/grunt|67446|将命令更新为以下命令后，它不再有内存错误：|67447|node+--max_old_space_size=2048+./node_modules/.bin/grunt+|67448|entityMap^0|E|I|17|I|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|15|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|U|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|V|$]]

I found that <code>max_new_space_size</code> is not an option in node 4.1.1 and <code>max_old_space_size</code> alone did not solve my problem. I am adding the following to my shebang and the combination of these seems to work:

<pre><code>#!/usr/bin/env node --max_old_space_size=4096 --optimize_for_size --max_executable_size=4096 --stack_size=4096
</code></pre>

[EDIT]: 4096 === 4GB of memory, if your device is low on memory you may want to choose a smaller amount. 

[UPDATE]: Also discovered this error while running grunt which previously was run like so:

<pre><code>./node_modules/.bin/grunt
</code></pre>

After updating the command to the following it stopped having memory errors:

<pre><code>node --max_old_space_size=2048 ./node_modules/.bin/grunt 
</code></pre>

blocks|key|4574023|text|我在这个问题上浪费了几天时间……直到我发现在某个文件中，我正在导入一个静态文件，一个构建文件。它使得构建永远不会结束。类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574024|import+PropTypes+from+"../static/build/prop-types";+|code-block|syntax|javascript|4574025|修复到真正的源代码解决了所有问题。|4574026|分享我的解决方案。:)|4574027|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I lost some days with this problem.... until I found that in some file I was importing one static file, a built file. It make the build to never end. Something like:

<pre><code>import PropTypes from "../static/build/prop-types"; 
</code></pre>

Fixing to the real source solved all the problem.

Sharing my solution. :)

blocks|key|67612|text|这只是上面答案的一个变体。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|67613|我尝试了上面的直接节点命令，但没有成功，但this+Angular+CLI+issue的建议对我有效-您可以在package.json文件中创建一个节点脚本，以在运行生产构建时增加节点可用的内存。|offset|length|style|CODE|67614|因此，如果您想将Node的可用内存增加到4+4gb+(max-old-space-size=4096)，那么您的Node命令应该是node+--max-old-space-size=4096+./node_modules/@angular/cli/bin/ng+build+--prod。(根据您的需要增加或减少内存量-4+4gb适合我，但您可能需要更多或更少)。然后将其添加到您的package.json“脚本”部分，如下所示：|67615|"prod":+"node+--max-old-space-size=4096+./node_modules/@angular/cli/bin/ng+build+--prod"|67616|它将与其他可用的脚本一起包含在脚本对象中-例如：|67617|"scripts":+{
++++"ng":+"ng",
++++"start":+"ng+serve",
++++"build":+"ng+build",
++++"test":+"ng+test",
++++"lint":+"ng+lint",
++++"e2e":+"ng+e2e",
++++"prod":+"node+--max-old-space-size=4096./node_modules/@angular/cli/bin/ng+build+--prod"
}|code-block|syntax|javascript|67618|你可以通过调用npm+run+prod来运行它(如果你使用的是Mac或者Linux，你可能需要运行sudo+npm+run+prod+)。|67619|注意，可能存在一个导致Node需要更多内存的潜在问题-如果是这样的话，这并没有解决这个问题-但它至少为Node提供了执行构建所需的内存。|67620|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/angular/angular-cli/issues/5618^0|0|1J|C|L|M|0|0|R|N|1T|26|0|0|2G|0|0|0|7|C|1D|H|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|H|3|I|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@$D|1H|E|1I|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1J|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1K|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1L|8|@$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Just a variation on the answers above. 

I tried the straight up node command above without success, but the suggestion from <a href="https://github.com/angular/angular-cli/issues/5618" rel="noreferrer">this Angular CLI issue</a> worked for me - you create a Node script in your <code>package.json</code> file to increase the memory available to Node when you run your production build. 

So if you want to increase the memory available to Node to 4gb (<code>max-old-space-size=4096</code>), your Node command would be <code>node --max-old-space-size=4096 ./node_modules/@angular/cli/bin/ng build --prod</code>. (increase or decrease the amount of memory depending on your needs as well - 4gb worked for me, but you may need more or less). You would then add it to your package.json 'scripts' section like this: 

<code>"prod": "node --max-old-space-size=4096 ./node_modules/@angular/cli/bin/ng build --prod"</code>

It would be contained in the scripts object along with the other scripts available - e.g.:

<pre><code>"scripts": {
 "ng": "ng",
 "start": "ng serve",
 "build": "ng build",
 "test": "ng test",
 "lint": "ng lint",
 "e2e": "ng e2e",
 "prod": "node --max-old-space-size=4096./node_modules/@angular/cli/bin/ng build --prod"
}
</code></pre>

And you run it by calling <code>npm run prod</code> (you may need to run <code>sudo npm run prod</code> if you're on a Mac or Linux).

Note there may be an underlying issue which is causing Node to need more memory - this doesn't address that if that's the case - but it at least gives Node the memory it needs to perform the build.

blocks|key|4574127|text|另一种解决方案是禁用AOT编译器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574128|ng+build+--prod+--aot+false|code-block|syntax|javascript|4574129|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

An alternative solution is to disable the AOT compiler:

<pre><code>ng build --prod --aot false
</code></pre>

blocks|key|4574162|text|当分配用于执行的内存少于运行进程所需的内存时，会发生此错误。默认情况下，节点内存大小为512+mb。要增加此大小，您需要键入以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574163|node+--max-old-space-size=+<NewSize>+<fileName>|code-block|syntax|javascript|4574164|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

this error occurs when required memory allocated for execution is less than memory required for running process. By default, Node memory size is 512 mb to increase this you need to type the following command :

<pre><code>node --max-old-space-size= &lt;NewSize&gt; &lt;fileName&gt;
</code></pre>

blocks|key|4574208|text|任何人在Azure生成管道中遇到此错误时，请尝试以下步骤来更改生成代理的环境变量|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574209|使用以下设置在编译前添加Azure+build+pipeline+task+->+Azure+powershell+script:Inlinescript|offset|length|style|CODE|4574210|-+task:+AzurePowerShell@3
++displayName:+'Azure+PowerShell+script:+InlineScript'
++inputs:
++++azureSubscription:+'NYCSCA+Azure+Dev/Test+(ea91a274-55c6-461c-a11d-758ef02c2698)'
++++ScriptType:+InlineScript
++++Inline:+'[Environment]::SetEnvironmentVariable("NODE_OPTIONS",+"--max_old_space_size=16384",+"Machine")'
++++FailOnStandardError:+true
++++azurePowerShellVersion:+LatestVersion|code-block|syntax|javascript|4574211|entityMap^0|0|C|P|15|10|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Anyone getting this error with Azure build pipelines, try the below step to change environment variable of build agent

Add an <code>Azure build pipeline task</code> -> <code>Azure powershell script:Inlinescript</code> before Compile with below settings

<pre><code>- task: AzurePowerShell@3
 displayName: 'Azure PowerShell script: InlineScript'
 inputs:
 azureSubscription: 'NYCSCA Azure Dev/Test (ea91a274-55c6-461c-a11d-758ef02c2698)'
 ScriptType: InlineScript
 Inline: '[Environment]::SetEnvironmentVariable("NODE_OPTIONS", "--max_old_space_size=16384", "Machine")'
 FailOnStandardError: true
 azurePowerShellVersion: LatestVersion
</code></pre>

blocks|key|4574294|text|#!/usr/bin/env+node+--+in+app-scripts.js+dint中的max-old-space-size=4096|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574295|但在修改之后：|4574296|node_modules/.bin/ionic-app-scripts.cmd|4574297|通过添加：|4574298|@IF+EXIST“"%25~dp0..@ionic\app-scripts\bin\ionic-app-scripts.js”“(”SET“"%25~dp0..@ionic\app-scripts\bin\ionic-app-scripts.js”%25*+)+ELSE+(+@SETLOCAL+@SET空间节点--%25~dp0\node.exe_%25~dp0\node.exe_+PATHEXT=%25PATHEXT:;.JS;=;%25+_size=4096+size+%25*+)|4574299|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

#!/usr/bin/env node --max-old-space-size=4096 in the ionic-app-scripts.js dint work
But after Modifying: the following file it worked
node_modules/.bin/ionic-app-scripts.cmd
By adding:
@IF EXIST &quot;%~dp0\node.exe&quot; (
&quot;%~dp0\node.exe&quot; &quot;%~dp0..@ionic\app-scripts\bin\ionic-app-scripts.js&quot; %*
) ELSE (
@SETLOCAL
@SET PATHEXT=%PATHEXT:;.JS;=;%
node --max_old_space_size=4096 &quot;%~dp0..@ionic\app-scripts\bin\ionic-app-scripts.js&quot; %*
)

blocks|key|67845|text|您还应该检查是否意外安装了node的x86版本，而不是x64。发生在我身上，因为nodejs.org在我的x64机器上预先选择了x86+...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|67846|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should also check if you accidentally installed the x86 version of node instead of x64. Happened to me, because nodejs.org preselected x86 on my x64 machine...

Node version is <code>v0.11.13</code>

Memory usage during crash according to <code>sudo top</code> not raises over <code>3%</code>

Code that reproduces this error:

<pre><code>var request = require('request')
var nodedump = require('nodedump')

request.get("http://pubapi.cryptsy.com/api.php?method=marketdatav2",function(err,res)
{
 var data
 console.log( "Data received." );
 data = JSON.parse(res.body)
 console.log( "Data parsed." );
 data = nodedump.dump(data)
 console.log( "Data dumped." ); 
 console.log( data )
})
</code></pre>

To check if that a recursion stack size problem I have ran next code with --stack-size=60000 parameter

<pre><code>var depth = 0;

(function recurse() {
 // log at every 500 calls
 (++depth % 500) || console.log(depth);
 recurse();
})();
</code></pre>

and have got

<pre><code>264500 
Segmentation fault
</code></pre>

Then I ran code which gives me FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory with the same --stack-size=60000 parameter and haven't got <code>Segmentation fault</code>. 

So I conclude <code>CALL_AND_RETRY_LAST</code> has nothing common with the recursion stack size.

How could I solve this problem? I believe there is enough free memory on my computer to finish this task successfully.

There are similar questions on stackoverflow but none of this questions are about <code>CALL_AND_RETRY_LAST</code> that's why I created separate question.

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

编译器

Linux

JSON

节点版本为v0.11.13崩溃期间的内存使用量根据sudo top不会在3%上引发重现此错误的代码：var request = require('request')var nodedump = require('nodedump')request.get("http://pubapi.cryptsy.com/api.p...

问致命错误: CALL_AND_RETRY_LAST分配失败-进程内存不足
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误: CALL_AND_RETRY_LAST分配失败-进程内存不足EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误: CALL_AND_RETRY_LAST分配失败-进程内存不足
EN