abort at exit_handler

NorbertThoden

Hi!

The following stack trace has been observed several times on our customer system:

System:

- V100.8

- Qt 5.15
- openSUSE Leap 15.1 @ 64Bit

Unfortunately i have no information about the circumstances under which this error occurs...

Thanks in advance for any hints 🙂

#0 0x00007f3f7def0520 in raise () at /lib64/libc.so.6
#1 0x00007f3f7def1b01 in abort () at /lib64/libc.so.6
#2 0x00007f3f7ec400bb in qErrnoWarning(char const*, ...) () at /usr/lib64/libQt5Core.so.5
#3 0x00007f3f7ec6193d in QThread::~QThread() () at /usr/lib64/libQt5Core.so.5
#4 0x00007f3f5b622fc9 in QRTImpl::(anonymous namespace)::Q_QGS_eventLoopThreadInstance::innerFunction()::Holder::~Holder() () at /usr/lib64/libEsriCommonQt.so
#5 0x00007f3f7def3138 in __run_exit_handlers () at /lib64/libc.so.6
#6 0x00007f3f7def318a in () at /lib64/libc.so.6
#7 0x00007f3f74785055 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5XcbQpa.so.5
#8 0x00007f3f747a9ba3 in () at /usr/lib64/libQt5XcbQpa.so.5
#9 0x00007f3f78e62e87 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#10 0x00007f3f78e63230 in () at /usr/lib64/libglib-2.0.so.0
#11 0x00007f3f78e632bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#12 0x00007f3f7eebb58c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#13 0x00007f3f7ee577ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#14 0x00007f3f7ee60fb7 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#15 0x00000000004060e8 in ()
#16 0x00007f3f7dedb34a in __libc_start_main () at /lib64/libc.so.6
#17 0x00000000004071fa in ()

JamesBallard1

Hi Norbert Thoden‌,

   I am familiar with parts of the stack trace, but we would need some more information to diagnose the problem.

Do you know if this only happens at shutdown? It looks like __run_exit_handlers is getting invoked which is cleaning up some internal global statics we have, and that is aborting. But it is curious since the applications seems to be shutting down already.

I saw this online c++ - Why does my application crash sometimes with a SIGSEGV when it gets closed? - Stack Overflow. This is a random guess, but is it possible the Runtime C++ API library is getting linked twice into the application? That library is a static library, libEsriRuntimeQt.a.

The static in question is located in libEsriCommonQt.so, but it may be getting loaded/initialized twice if libEsriRuntimeQt.a is linked twice into the application somehow.