GC segfault

[Smbc1]

Known error (nodejs/node-v0.x-archive#25648) with segfault when using --expose-gc repeats on node 5.0.0

Here is callstack:

PID 2614 received SIGSEGV for address: 0xffffffffffffffa0
/<path to modules>/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1a13)[0x7f91d067ba13]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f91d14190a0]
next engine worker(_ZN2v88internal23PointersUpdatingVisitor12VisitPointerEPPNS0_6ObjectE+0x18)[0x99f6c8]
next engine worker(_ZN2v88internal13ObjectVisitor14VisitCodeEntryEPh+0x28)[0xac3988]
next engine worker(_ZN2v88internal20MarkCompactCollector29EvacuateNewSpaceAndCandidatesEv+0xeb9)[0x9bf249]
next engine worker(_ZN2v88internal20MarkCompactCollector11SweepSpacesEv+0x2f1)[0x9e4c51]
next engine worker(_ZN2v88internal20MarkCompactCollector14CollectGarbageEv+0x2a)[0x9ec90a]
next engine worker(_ZN2v88internal4Heap11MarkCompactEv+0x9f)[0x96882f]
next engine worker(_ZN2v88internal4Heap24PerformGarbageCollectionENS0_16GarbageCollectorENS_15GCCallbackFlagsE+0x288)[0x97c938]
next engine worker(_ZN2v88internal4Heap14CollectGarbageENS0_16GarbageCollectorEPKcS4_NS_15GCCallbackFlagsE+0xce)[0x97cf5e]
next engine worker(_ZN2v88internal4Heap17CollectAllGarbageEiPKcNS_15GCCallbackFlagsE+0x6c)[0x97d37c]
next engine worker(_ZN2v87Isolate34RequestGarbageCollectionForTestingENS0_21GarbageCollectionTypeE+0x3d)[0x80598d]
next engine worker(_ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE+0x9c)[0x82b78c]
next engine worker[0x84ddff]
[0x36cfbc2060a2]

[evanlucas]

Is there a reproducible test case that you can share with us to help identify the issue?

[calzoneman]

Not sure if this is related, but this consistently dumps core after 5 iterations of the while loop on my machine (Arch Linux, node.js v5.0.0):

var x = [];

while (true) {
    for (var i = 0; i < 10000000; i++) x.push(Math.random());
    console.log(process.memoryUsage().rss / 1000000);
}

[cjihrig]

@calzoneman I don't think they're related. In your case, the process seems to be running out of memory by continuously pushing to x.

[calzoneman]

It's not running out of memory (it crashes after only reaching ~1.1GB rss), I think I've tracked it down to v8 having a length limit on arrays. But you're right, I think it's unrelated.

[calzoneman]

Getting this on node v4.2.2 as well, when using --expose-gc:

#0  0x0000000000aec14b in v8::internal::PointersUpdatingVisitor::VisitPointer(v8::internal::Object**) ()
#1  0x0000000000bea673 in v8::internal::ObjectVisitor::VisitCodeEntry(unsigned char*) ()
#2  0x0000000000aef867 in v8::internal::SlotsBuffer::UpdateSlots(v8::internal::Heap*) ()
#3  0x0000000000af31ba in v8::internal::MarkCompactCollector::EvacuateNewSpaceAndCandidates() ()
#4  0x0000000000af4a03 in v8::internal::MarkCompactCollector::SweepSpaces() ()
#5  0x0000000000afe778 in v8::internal::MarkCompactCollector::CollectGarbage() ()
#6  0x0000000000ab5030 in v8::internal::Heap::MarkCompact() ()
#7  0x0000000000acc948 in v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) ()
#8  0x0000000000accee9 in v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, char const*, char const*, v8::GCCallbackFlags) ()
#9  0x0000000000acd1e5 in v8::internal::Heap::CollectAllGarbage(int, char const*, v8::GCCallbackFlags) ()
#10 0x00000000008f2837 in v8::Isolate::RequestGarbageCollectionForTesting(v8::Isolate::GarbageCollectionType) ()
#11 0x0000000000903fa2 in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) ()
#12 0x000000000092de61 in v8::internal::MaybeHandle<v8::internal::Object> v8::internal::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>&) ()
#13 0x000000000092e2be in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) ()
...

I'll see if I can dumb it down to a testcase, but it happens very intermittently so I haven't been able to track down what triggers it.

[artofspeed]

happens to me too with v4.3.0 and v4.3.2

[MylesBorins]

have you tried v4.4.0

[artofspeed]

just tried, happened on 4.4.0 as well after 1 day of running

[MylesBorins]

@artofspeed do you have a minimal test case?