Bug 343362 - Random crashes in KMail while being "inactive"
Summary: Random crashes in KMail while being "inactive"
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-27 10:52 UTC by Wolfgang Brehm
Modified: 2016-04-13 12:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.03 KB, text/plain)
2015-03-15 12:39 UTC, Wolfgang Brehm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Brehm 2015-01-27 10:52:22 UTC
KMail sometimes crashes at seemingly random times in intervals of months.
I am using the application every day and to this day it has only crashed while being "inactive" in the system tray without my Interaction.

possible duplicate of bug 325467

Reproducible: Sometimes

Steps to Reproduce:
1.Have KMail installed
2.Wait
3.Wait more

Actual Results:  
it crashes

Expected Results:  
it should run forever

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

Thread 5 (Thread 0x7f4df3c63700 (LWP 1607)):
#0  0x00007f4e152b7a63 in select () at /lib64/libc.so.6
#1  0x00007f4e168c10df in  () at /usr/lib64/libQtCore.so.4
#2  0x00007f4e167e279f in  () at /usr/lib64/libQtCore.so.4
#3  0x00007f4e130bf0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f4e152be7fd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f4df21a3700 (LWP 1662)):
#0  0x00007f4e130c305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f4e085f0686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f4e085f06b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f4e130bf0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f4e152be7fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4df1012700 (LWP 1754)):
#0  0x00007f4e130c305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f4e08362e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f4e086181e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f4e130bf0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f4e152be7fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f4dabffd700 (LWP 1771)):
[KCrash Handler]
#5  0x00007f4e0ad5fb3e in  () at /lib64/libdbus-1.so.3
#6  0x00007f4e0ad58bc2 in  () at /lib64/libdbus-1.so.3
#7  0x00007f4e0ad590d2 in dbus_message_unref () at /lib64/libdbus-1.so.3
#8  0x00007f4e13323b09 in QDBusArgument::~QDBusArgument() () at /usr/lib64/libQtDBus.so.4
#9  0x00007f4e1330076e in  () at /usr/lib64/libQtDBus.so.4
#10 0x00007f4e169079a3 in  () at /usr/lib64/libQtCore.so.4
#11 0x00007f4e132efa5c in  () at /usr/lib64/libQtDBus.so.4
#12 0x00007f4e13303f7f in QDBusMessage::~QDBusMessage() () at /usr/lib64/libQtDBus.so.4
#13 0x00007f4e13300d56 in  () at /usr/lib64/libQtDBus.so.4
#14 0x00007f4e168e7586 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#15 0x00007f4e169118fe in  () at /usr/lib64/libQtCore.so.4
#16 0x00007f4e0ce1ba04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#17 0x00007f4e0ce1bc48 in  () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f4e0ce1bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f4e169110de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#20 0x00007f4e168e2e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#21 0x00007f4e168e3165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#22 0x00007f4e167e00bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#23 0x00007f4e167e279f in  () at /usr/lib64/libQtCore.so.4
#24 0x00007f4e130bf0a4 in start_thread () at /lib64/libpthread.so.0
#25 0x00007f4e152be7fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4e17f55800 (LWP 1385)):
#0  0x00007f4e152b249d in read () at /lib64/libc.so.6
#1  0x00007f4e0ce5c750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f4e0ce1b714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f4e0ce1bb7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f4e0ce1bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f4e169110de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f4e15d1a676 in  () at /usr/lib64/libQtGui.so.4
#7  0x00007f4e168e2e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#8  0x00007f4e168e3165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#9  0x00007f4e168e85b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#10 0x0000000000402f3f in  ()
#11 0x00007f4e151fab05 in __libc_start_main () at /lib64/libc.so.6
#12 0x0000000000403414 in _start ()
Comment 1 Wolfgang Brehm 2015-02-19 15:25:41 UTC
Happened again

Application: kmail (4.14.4)
KDE Platform Version: 4.14.4
Qt Version: 4.8.6
Operating System: Linux 3.16.7-7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
Reproducible: Sometimes

Steps to Reproduce:
1.Have KMail installed
2.Wait
3.Wait more

Actual Results:  
it crashes

Expected Results:  
it should run forever

The crash can be reproduced sometimes.

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

Thread 4 (Thread 0x7f971d9e9700 (LWP 1746)):
#0  0x00007f973e91905f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f9733e34686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f9733e346b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f973e9150a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f9740b147fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f971c858700 (LWP 1808)):
#0  0x00007f973e91905f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f9733ba6e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f9733e5c1e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f973e9150a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f9740b147fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f96d79ce700 (LWP 1812)):
[KCrash Handler]
#5  0x00007f97365a3b3e in  () at /lib64/libdbus-1.so.3
#6  0x00007f973659cbc2 in  () at /lib64/libdbus-1.so.3
#7  0x00007f973659d0d2 in dbus_message_unref () at /lib64/libdbus-1.so.3
#8  0x00007f973eb79b09 in QDBusArgument::~QDBusArgument() () at /usr/lib64/libQtDBus.so.4
#9  0x00007f973eb5676e in  () at /usr/lib64/libQtDBus.so.4
#10 0x00007f974215d9a3 in  () at /usr/lib64/libQtCore.so.4
#11 0x00007f973eb45a5c in  () at /usr/lib64/libQtDBus.so.4
#12 0x00007f973eb59f7f in QDBusMessage::~QDBusMessage() () at /usr/lib64/libQtDBus.so.4
#13 0x00007f973eb56d56 in  () at /usr/lib64/libQtDBus.so.4
#14 0x00007f974213d586 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#15 0x00007f97421678fe in  () at /usr/lib64/libQtCore.so.4
#16 0x00007f973865fa04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#17 0x00007f973865fc48 in  () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f973865fcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f97421670de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#20 0x00007f9742138e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#21 0x00007f9742139165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#22 0x00007f97420360bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#23 0x00007f974203879f in  () at /usr/lib64/libQtCore.so.4
#24 0x00007f973e9150a4 in start_thread () at /lib64/libpthread.so.0
#25 0x00007f9740b147fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f97437b1800 (LWP 1471)):
#0  0x00007f9740b0849d in read () at /lib64/libc.so.6
#1  0x00007f97386a0750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f973865f714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f973865fb7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f973865fcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f97421670de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f9741570676 in  () at /usr/lib64/libQtGui.so.4
#7  0x00007f9742138e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#8  0x00007f9742139165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#9  0x00007f974213e5b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#10 0x0000000000402f3f in  ()
#11 0x00007f9740a50b05 in __libc_start_main () at /lib64/libc.so.6
#12 0x0000000000403414 in _start ()
Comment 2 Wolfgang Brehm 2015-03-15 12:39:56 UTC
Created attachment 91566 [details]
New crash information added by DrKonqi

kmail (4.14.5) on KDE Platform 4.14.5 using Qt 4.8.6

I did nothing - as usual this occurs while Kmail is idle.

-- Backtrace (Reduced):
#5  0x00007f9d94c7eb3e in  () at /lib64/libdbus-1.so.3
#6  0x00007f9d94c77bc2 in  () at /lib64/libdbus-1.so.3
[...]
#8  0x00007f9d9d26cb09 in QDBusArgument::~QDBusArgument() () at /usr/lib64/libQtDBus.so.4
#9  0x00007f9d9d24976e in  () at /usr/lib64/libQtDBus.so.4
#10 0x00007f9da084f9a3 in  () at /usr/lib64/libQtCore.so.4
Comment 3 Wolfgang Brehm 2015-03-20 22:37:00 UTC
I have noticed that after a zypper dup this happens with an increased propability.
I sadly cannot rule out the possibility that I had made a zypper dup for the past two backtraces. So there might be a mundane explanation for the crashes. Or not. I will keep an eye open, will be especially carefull and only report if it crashes without a prior zypper anything.
Comment 4 Wolfgang Brehm 2016-04-13 12:50:18 UTC
It seems to me that it is either fixed or more probably was my fault all along.