FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

[huan]

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x89375c [node]
 3: v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xe616b2 [node]
 6: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 7: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 8: v8::internal::Heap::AllocateRawWithRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
 9: v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
10: v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
11: 0x17b7da5841bd
12:56:22 WARN PuppetPadchat onPadchatMessageRoomEvent() case PadchatMesssageSys: inviterId found more than 1, use the first one.
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x89375c [node]
 3: v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xe616b2 [node]
 6: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 7: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 8: v8::internal::Heap::AllocateRawWithRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
 9: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [node]
10: v8::internal::String::SlowFlatten(v8::internal::Handle<v8::internal::ConsString>, v8::internal::PretenureFlag) [node]
11: v8::internal::String::Flatten(v8::internal::Handle<v8::internal::String>, v8::internal::PretenureFlag) [node]
12: v8::internal::Runtime_RegExpExecMultiple(int, v8::internal::Object**, v8::internal::Isolate*) [node]
13: 0x2dc749f041bd

See

By default the memory limit in Node js is 512mb/1.7GB(dependes on version, not confirmed). This will cause FATAL ERROR- JS Allocation failed – process out of memory when processing large data files. It can be avoided by increasing the memory limit.

• Does my NodeJS application leak memory? – 5
• Increasing Node.js memory limits

[huan]

node --max-old-space-size=3049 my-node-script.js

[huan]

With TypeScript

node -r ts-node/register --max-old-space-size

See

• Pass --max-old-space-size flag through to Node TypeStrong/ts-node#261 (comment)
• ts-node v5.0 release note: https://github.com/TypeStrong/ts-node/releases/tag/v5.0.0

[windmemory]

How to increase the size with the docker image?

[huan]

I'm still investigating with it and will let you know when I get any update of it by reply this issue.

[windmemory]

Besides, when did you see the error got thrown? What was the operation that triggered this heap OOM?

[huan]

I can reproduce this problem at any time.

What's your operation that triggered this heap oom?

[windmemory]

Mine was doing contact.finaAll with name as an argument. And the problem fixed by changing the contact.findAll to contact.load with contactId

[huan]

Close this issue because it seems had been fixed with the latest code.

[jayarjo]

Hitting this with the version 2.1.1.

[najibkh]

node --max-old-space-size=4096 my-node-script.js

i tried it but i still got the error