Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Incomplete
-
3.8.4, 3.9.1
-
None
-
None
Description
During shutdown of our application there seem to still be ActiveMQ-CPP threads running which rarely cause a segfault. Attached is an analysis of the core file from one of these instances. The stack trace of the thread which caused the segfault was:
Program terminated with signal 11, Segmentation fault.
#0 0x0000003619689adf in memcpy () from /lib64/libc.so.6
#0 0x0000003619689adf in memcpy () from /lib64/libc.so.6
#1 0x0000003624a9dadc in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::append(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib64/libstdc++.so.6
#2 0x00002ba8ca62d152 in MutexProperties (this=0x2ba8d81ffb40) at decaf/util/concurrent/Mutex.cpp:50
#3 decaf::util::concurrent::Mutex::Mutex (this=0x2ba8d81ffb40) at decaf/util/concurrent/Mutex.cpp:78
#4 0x00002ba8ca63c3ee in AbstractCollection (this=0x22bd960) at ./decaf/util/AbstractCollection.h:65
#5 AbstractList (this=0x22bd960) at ./decaf/util/AbstractList.h:341
#6 AbstractSequentialList (this=0x22bd960) at ./decaf/util/AbstractSequentialList.h:59
#7 LinkedList (this=0x22bd960) at ./decaf/util/LinkedList.h:91
#8 decaf::util::concurrent::ExecutorKernel::WorkerKiller::run (this=0x22bd960) at decaf/util/concurrent/ThreadPoolExecutor.cpp:248
#9 0x00002ba8ca6270c2 in decaf::util::TimerImpl::run (this=0x23b32a0) at decaf/util/Timer.cpp:156
#10 0x00002ba8ca5a612f in (anonymous namespace)::runCallback (arg=0x226a890) at decaf/internal/util/concurrent/Threading.cpp:268
#11 0x00002ba8ca5a5ea4 in (anonymous namespace)::threadEntryMethod (arg=0x226a890) at decaf/internal/util/concurrent/Threading.cpp:256
#12 0x000000361a207aa1 in start_thread () from /lib64/libpthread.so.0
#13 0x00000036196e8aad in clone () from /lib64/libc.so.6