Hello,
We are using couchbase community edition “couchbase-server-community-4.1.0-5005.x86_64” running in RHEL Release 7.2
We are facing an issue where beam process is getting coredumped.
It seems to be segmentation fault.
Following is the backtrace details.
(gdb) bt
#0 0x00007f41dba8f6c6 in v8::internal::MarkCompactCollector::MigrateObject(unsigned char*, unsigned char*, int, v8::internal::AllocationSpace) ()
from /opt/couchbase/lib/libv8.so
#1 0x00007f41dba8f8db in v8::internal::MarkCompactCollector::TryPromoteObject(v8::internal::HeapObject*, int) () from /opt/couchbase/lib/libv8.so
#2 0x00007f41dba8fbd5 in v8::internal::MarkCompactCollector::DiscoverAndPromoteBlackObjectsOnPage(v8::internal::NewSpace*, v8::internal::NewSpacePage*) ()
from /opt/couchbase/lib/libv8.so
#3 0x00007f41dba8fe9c in v8::internal::MarkCompactCollector::EvacuateNewSpace() () from /opt/couchbase/lib/libv8.so
#4 0x00007f41dba9f7b8 in v8::internal::MarkCompactCollector::EvacuateNewSpaceAndCandidates() () from /opt/couchbase/lib/libv8.so
#5 0x00007f41dbaa219d in v8::internal::MarkCompactCollector::SweepSpaces() () from /opt/couchbase/lib/libv8.so
#6 0x00007f41dbaa228b in v8::internal::MarkCompactCollector::CollectGarbage() () from /opt/couchbase/lib/libv8.so
#7 0x00007f41db9d9d2c in v8::internal::Heap::MarkCompact(v8::internal::GCTracer*) () from /opt/couchbase/lib/libv8.so
#8 0x00007f41db9e066b in v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GCTracer*) () from /opt/couchbase/lib/libv8.so
#9 0x00007f41db9e09dd in v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollector, char const*, char const*) ()
from /opt/couchbase/lib/libv8.so
#10 0x00007f41db9e0c83 in v8::internal::Heap::CollectAllGarbage(int, char const*) () from /opt/couchbase/lib/libv8.so
#11 0x00007f41db9844f2 in v8::internal::Execution::HandleStackGuardInterrupt(v8::internal::Isolate*) () from /opt/couchbase/lib/libv8.so
#12 0x000000855d0072ce in ?? ()
#13 0x000000855d007221 in ?? ()
#14 0x00007f4217938800 in ?? ()
#15 0x00007f4217938848 in ?? ()
#16 0x000000855d03ee06 in ?? ()
#17 0x00007f41900029e0 in ?? ()
#18 0x00007f419000a300 in ?? ()
#19 0x00000000000044a0 in ?? ()
#20 0x00002937b53520e1 in ?? ()
#21 0x00002937b534a221 in ?? ()
#22 0x00007f4217938888 in ?? ()
#23 0x000000855d010f14 in ?? ()
#24 0x00002937b5304121 in ?? ()
#25 0x00000110d4f0dbd9 in ?? ()
#26 0x00002937b5352031 in ?? ()
#27 0x0000000100000000 in ?? ()
#28 0x00002937b53520e1 in ?? ()
#29 0x0000000a00000000 in ?? ()
#30 0x00007f42179388c8 in ?? ()
#31 0x000000855d02e3de in ?? ()
#32 0x00000110d4f0dbd9 in ?? ()
#33 0x00002937b5352031 in ?? ()
#34 0x00002937b53520e1 in ?? ()
#35 0x000000855d02e321 in ?? ()
#36 0x0000000800000000 in ?? ()
#37 0x0000000000000000 in ?? ()
(gdb)
/var/log/mesages, couchbase info logs, corefile snapshot and backtrace is uploaded to following link.
couchbase_forum_data.zip (2.7 MB)
Request to let us know the reason for this coredump of beam. Is it part of any bug.
Regards
Pratheej