[kmail2] [Bug 342879] Crashes out of the blue

Fabian Vogt fabian at ritter-vogt.de
Mon Jan 19 22:38:14 GMT 2015


https://bugs.kde.org/show_bug.cgi?id=342879

--- Comment #2 from Fabian Vogt <fabian at ritter-vogt.de> ---
Got another crash, with debug info for kmail:

Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3dc9916800 (LWP 1407))]

Thread 4 (Thread 0x7f3da4317700 (LWP 1613)):
#0  0x00007f3dc4a8a05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x00007f3db9fb8686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x00007f3db9fb86b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f3dc4a860a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f3dc6c857fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3d63174700 (LWP 1630)):
#0  0x00007f3dc4a8a05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x00007f3db9d2ae7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x00007f3db9fe01e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x00007f3dc4a860a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f3dc6c857fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f3d622d6700 (LWP 1633)):
[KCrash Handler]
#5  0x00007f3dbc727b3e in  () at /lib64/libdbus-1.so.3
#6  0x00007f3dbc720bc2 in  () at /lib64/libdbus-1.so.3
#7  0x00007f3dbc7210d2 in dbus_message_unref () at /lib64/libdbus-1.so.3
#8  0x00007f3dc4ceab09 in QDBusArgument::~QDBusArgument() () at
/usr/lib64/libQtDBus.so.4
#9  0x00007f3dc4cc776e in  () at /usr/lib64/libQtDBus.so.4
#10 0x00007f3dc82ce9a3 in  () at /usr/lib64/libQtCore.so.4
#11 0x00007f3dc4cb6a5c in  () at /usr/lib64/libQtDBus.so.4
#12 0x00007f3dc4ccaf7f in QDBusMessage::~QDBusMessage() () at
/usr/lib64/libQtDBus.so.4
#13 0x00007f3dc4cc7d56 in  () at /usr/lib64/libQtDBus.so.4
#14 0x00007f3dc82ae586 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#15 0x00007f3dc82d88fe in  () at /usr/lib64/libQtCore.so.4
#16 0x00007f3dbe7e2a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#17 0x00007f3dbe7e2c48 in  () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f3dbe7e2cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#19 0x00007f3dc82d80de in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#20 0x00007f3dc82a9e6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#21 0x00007f3dc82aa165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#22 0x00007f3dc81a70bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#23 0x00007f3dc81a979f in  () at /usr/lib64/libQtCore.so.4
#24 0x00007f3dc4a860a4 in start_thread () at /lib64/libpthread.so.0
#25 0x00007f3dc6c857fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3dc9916800 (LWP 1407)):
#0  0x00007f3dc6c7949d in read () at /lib64/libc.so.6
#1  0x00007f3dbe823750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f3dbe7e2714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007f3dbe7e2b7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f3dbe7e2cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x00007f3dc82d80de in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#6  0x00007f3dc76e1676 in  () at /usr/lib64/libQtGui.so.4
#7  0x00007f3dc82a9e6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#8  0x00007f3dc82aa165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#9  0x00007f3dc82af5b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#10 0x0000000000402f3f in main(int, char**) (argc=<optimized out>,
argv=<optimized out>) at /usr/src/debug/kdepim-4.14.3/kmail/main.cpp:145

It looks like it's actually DBus related, as the only common thread is #2. Any
idea how I could test whether it's kmail's fault or a bug in QtDBus?

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list