CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

[slim-hmidi]

• Node.js Version: 8.4.0
• OS: Ubuntu 17.04LTS

I'm using node v8.4.0 on ubuntu 17.04 and I'm trying to parse data from external data from an external api, when I run the program I got this error:

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x13740dc [node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewByteArray(int, v8::internal::PretenureFlag) [node]
 6: v8::internal::Factory::NewCode(v8::internal::CodeDesc const&, unsigned int, v8::internal::Handle<v8::internal::Object>, bool, bool, int, bool) [node]
 7: v8::internal::CodeGenerator::MakeCodeEpilogue(v8::internal::MacroAssembler*, v8::internal::EhFrameWriter*, v8::internal::CompilationInfo*, v8::internal::Handle<v8::internal::Object>) [node]
 8: v8::internal::compiler::CodeGenerator::FinalizeCode() [node]
 9: v8::internal::compiler::PipelineImpl::FinalizeCode() [node]
10: v8::internal::compiler::PipelineCompilationJob::FinalizeJobImpl() [node]
11: v8::internal::CompilationJob::FinalizeJob() [node]
12: v8::internal::Compiler::FinalizeCompilationJob(v8::internal::CompilationJob*) [node]
13: v8::internal::OptimizingCompileDispatcher::InstallOptimizedFunctions() [node]
14: v8::internal::StackGuard::HandleInterrupts() [node]
15: v8::internal::Runtime_StackGuard(int, v8::internal::Object**, v8::internal::Isolate*) [node]
16: 0x30ea1f8840dd
Aborted (core dumped)

How can I fix that?

[bnoordhuis]

If it consistently fails with CodeGenerator in the stack trace, then you probably have code in your application that calls eval() or new Function() a lot - so much so it causes the process to run out of memory.

Back-linking to nodejs/node#17878 for posterity.

[slim-hmidi]

it's not easy with debugger to detect what is the function that causes this error due to a lot of RxJS observables that I used to parse data from external api. Is there any way to detect the source of problem?

[bnoordhuis]

Try heap snapshots or heap profiling in the inspector.

[mikeRChambers610]

@slim-hmidi why was this closed? What is the solution?