Node: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

[loretoparisi]

<--- Last few GCs --->

 6428056 ms: Scavenge 1384.0 (1458.1) -> 1384.0 (1458.1) MB, 5.1 / 0 ms (+ 0.9 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
 6429707 ms: Mark-sweep 1384.0 (1458.1) -> 1383.8 (1458.1) MB, 1650.7 / 2 ms (+ 2.0 ms in 2 steps since start of marking, biggest step 1.1 ms) [last resort gc].
 6431355 ms: Mark-sweep 1383.8 (1458.1) -> 1383.8 (1458.1) MB, 1648.4 / 2 ms [last resort gc].


<--- JS stacktrace --->

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

Security context: 0x3adfe98e3ac1 <JS Object>
    2: populateURI [//node_modules/aws-sdk/lib/services/s3.js:~163] [pc=0x3d43348528ae] (this=0x36d637b2c239 <a Request with map 0x148a274595b1>,req=0x36d637b2c239 <a Request with map 0x148a274595b1>)
    4: callListeners [//node_modules/aws-sdk/lib/seq...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abort trap: 6

on

$ node -v
v5.5.0
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.12.1
BuildVersion:   16B2659

How to malloc?

[vsemozhetbyt]

By default, Node.js sets memory limit near 1.5 GB. Try to increase it by this key (this example sets 2 GB):

node --max_old_space_size=2048 script.js

[cjihrig]

I don't think there is anything for Node to do here, so I'm going to close. We can reopen if necessary.

[loretoparisi]

@cjihrig thanks I confirm that it was a memory issue, solved increasing memory limit more to 2048 solved it.