Bug 176688 - Kmail crash with SIGABRT
Summary: Kmail crash with SIGABRT
Status: RESOLVED DUPLICATE of bug 200137
Alias: None
Product: kmail
Classification: Applications
Component: GUI (show other bugs)
Version: 1.11.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 186154 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-02 10:44 UTC by tony
Modified: 2009-08-03 08:31 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash output (7.21 KB, application/octet-stream)
2009-02-17 17:17 UTC, tony
Details
GDB output (29.21 KB, application/octet-stream)
2009-02-17 17:18 UTC, tony
Details
Kmail crash output (5.79 KB, application/octet-stream)
2009-03-04 17:30 UTC, tony
Details
Result of attaching GDB to Kmail after the crash (27.75 KB, application/octet-stream)
2009-03-04 17:31 UTC, tony
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tony 2008-12-02 10:44:56 UTC
Version:           1.10.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

After starting up and reading a couple of messages, I had left my computer for a while and when I came back, Kmail  had crashed with a SIGABRT message. So I wasn't actually doing anything with it at the time that I can identify as the cause. It's POSSIBLE that it might have been expiring old messages at the time, as I have observed that it often takes a long time (and a lot of CPU) doing this after startup.

Backtrace follows:
Application: KMail (kmail), signal SIGABRT
(no debugging symbols found)              
(no debugging symbols found)              
[Thread debugging using libthread_db enabled]
[New Thread 0x7f8727c086f0 (LWP 7030)]       
[KCrash handler]                             
#5  0x00007f8724b05fd5 in raise () from /lib/libc.so.6
#6  0x00007f8724b07b43 in abort () from /lib/libc.so.6
#7  0x00007f87276566b5 in qt_message_output () from /usr/lib/libQtCore.so.4                                                                 
#8  0x00007f87276567fd in qFatal () from /usr/lib/libQtCore.so.4      
#9  0x00007f8726a31561 in ?? () from /usr/lib/libkmailprivate.so.4    
#10 0x00007f8726a30561 in ?? () from /usr/lib/libkmailprivate.so.4    
#11 0x00007f8726a7948f in ?? () from /usr/lib/libkmailprivate.so.4    
#12 0x00007f8726a2fff9 in ?? () from /usr/lib/libkmailprivate.so.4    
#13 0x00007f8726c19f66 in ?? () from /usr/lib/libkmailprivate.so.4    
#14 0x00007f8726c1a0b8 in ?? () from /usr/lib/libkmailprivate.so.4    
#15 0x00007f872775b134 in QMetaObject::activate ()                    
   from /usr/lib/libQtCore.so.4
#16 0x00007f8727755a43 in QObject::event () from /usr/lib/libQtCore.so.4
#17 0x00007f8725534c3d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0x00007f872553c9ea in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0x00007f87260dafcb in KApplication::notify (this=0x7fff2fc4f060,
    receiver=0x210a910, event=0x7fff2fc4ec00)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#20 0x00007f8727746d61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0x00007f8727772ab6 in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f872776f1fd in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007f8724221d3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#24 0x00007f872422550d in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x00007f87242256cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#26 0x00007f872776f15f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0x00007f87255c6a9f in ?? () from /usr/lib/libQtGui.so.4
#28 0x00007f8727745682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#29 0x00007f872774580d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0x00007f8727747cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#31 0x0000000000402fcb in _start ()
#0  0x00007f8724b7b5f0 in __nanosleep_nocancel () from /lib/libc.so.6
Comment 1 Jaime Torres 2008-12-02 12:31:22 UTC
Hi, thanks for your bug report.
Unfortunately, the backtrace you posted is not very useful. You can read in: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports 
further instructions on how to get a more detailed one. 
Thank you. 
Comment 2 tony 2008-12-02 12:48:55 UTC
(In reply to comment #1)
> Hi, thanks for your bug report.
> Unfortunately, the backtrace you posted is not very useful. You can read in:
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports 
> further instructions on how to get a more detailed one. 
> Thank you. 
> 

OK, I've installed the relevant debug packages and I'll run Kmail through gdb until it happens again. Fingers crossed...
Comment 3 Dario Andres 2009-01-07 19:31:18 UTC
Haven't you experienced this bug again?
Comment 4 tony 2009-01-07 19:34:16 UTC
Annoyingly, I ran Kmail through GDB every day for several weeks without a single crash. Then I forgot to do it that way and within a few days it crashed again.
Comment 5 Dario Andres 2009-01-07 19:37:38 UTC
And the KCrash handler didn't appeared ?
Comment 6 tony 2009-01-07 22:10:47 UTC
It did, but had no more useful information than the other times I wasn't running with GDB, unfortunately.
Comment 7 Jaime Torres 2009-01-09 18:47:55 UTC
If you have enought memory, you can try to run kmail using "valgrind kmail", it could bring some light.
Comment 8 tony 2009-01-09 19:54:31 UTC
Thanks Jaime, that's a lot simpler than GDB, because I can launch it automatically from the startup scripts rather than having to mess about with GDB. As soon as it happens again, I'll post the results.
Comment 9 Christophe Marin 2009-02-14 19:08:08 UTC
tony: any news about this crash ? Do you still experience it ? 
Comment 10 tony 2009-02-14 19:21:30 UTC
Hi Christophe.
It hasn't happened for some while. Either whatever I had in my mailboxes that triggered it is gone, or a subsequent code change has eliminated it.

I think the best idea would be to close this bug and I'll open a fresh one if I get a recurrence in the future.
Comment 11 tony 2009-02-17 17:12:53 UTC
With typical good timing, the crash recurred just three days after we decided to close the bug. I've taken a dump with GDB, so with a bit of luck this might be more useful than what I've caught previously.
Comment 12 tony 2009-02-17 17:17:53 UTC
Created attachment 31406 [details]
Crash output
Comment 13 tony 2009-02-17 17:18:24 UTC
Created attachment 31407 [details]
GDB output
Comment 14 tony 2009-03-04 17:25:20 UTC
Fell over again today while composing a reply to a message.
This is with Kmail 1.11.0/KDE 4.2.0
crash report and GDB output attached.
Comment 15 tony 2009-03-04 17:30:24 UTC
Created attachment 31775 [details]
Kmail crash output
Comment 16 tony 2009-03-04 17:31:11 UTC
Created attachment 31776 [details]
Result of attaching GDB to Kmail after the crash
Comment 17 Jaime Torres 2009-03-05 09:03:55 UTC
Pasting the interesting part of the backtrace.

#9  0x00007f7d766f8681 in FolderStorage::ignoreJobsForMessage (this=0xb37f70, msg=0x17c3da0) at /usr/include/qt4/QtCore/qlist.h:246
#10 0x00007f7d766f7111 in FolderStorage::unGetMsg (this=0xb37f70, idx=1) at /build/buildd/kdepim-4.2.0/kmail/folderstorage.cpp:569
#11 0x00007f7d76740fe6 in KMSearchPattern::matches (this=0xade950, serNum=<value optimized out>, ignoreBody=<value optimized out>) at /build/buildd/kdepim-4.2.0/kmail/kmsearchpattern.cpp:794
#12 0x00007f7d766f6b99 in FolderStorage::slotProcessNextSearchBatch (this=0xb37f70) at /build/buildd/kdepim-4.2.0/kmail/folderstorage.cpp:1171
#13 0x00007f7d768ea2c6 in KMSearch::slotProcessNextBatch (this=0xad87f0) at /build/buildd/kdepim-4.2.0/kmail/kmfoldersearch.cpp:272
#14 0x00007f7d768ea438 in KMSearch::qt_metacall (this=0xad87f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7fb5ee30)
    at /build/buildd/kdepim-4.2.0/obj-x86_64-linux-gnu/kmail/kmfoldersearch.moc:78
#15 0x00007f7d73219134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007f7d73213a43 in QObject::event () from /usr/lib/libQtCore.so.4
#17 0x00007f7d73928c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#18 0x00007f7d739309ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0x00007f7d775575db in KApplication::notify (this=0x7fff7fb62e50, receiver=0xadb150, event=0x7fff7fb5f4e0) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#20 0x00007f7d73204d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#21 0x00007f7d73230ab6 in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f7d7322d1fd in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007f7d6a925d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0x00007f7d6a92950d in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x00007f7d6a9296cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0x00007f7d7322d15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#27 0x00007f7d739baa6f in ?? () from /usr/lib/libQtGui.so.4
#28 0x00007f7d73205e29 in QCoreApplication::processEvents () from /usr/lib/libQtCore.so.4
#29 0x00007f7d767f07f0 in KMKernel::dumpDeadLetters (this=<value optimized out>) at /build/buildd/kdepim-4.2.0/kmail/kmkernel.cpp:1813
#30 0x00007f7d775bd501 in KCrash::defaultCrashHandler (sig=6) at /build/buildd/kde4libs-4.2.0/kdeui/util/kcrash.cpp:224
#31 <signal handler called>
#32 0x00007f7d725c7015 in raise () from /lib/libc.so.6
#33 0x00007f7d725c8b83 in abort () from /lib/libc.so.6
#34 0x00007f7d731146b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#35 0x00007f7d731147fd in qFatal () from /usr/lib/libQtCore.so.4
#36 0x00007f7d766f8681 in FolderStorage::ignoreJobsForMessage (this=0xb37f70, msg=0x285e620) at /usr/include/qt4/QtCore/qlist.h:246
#37 0x00007f7d766f7111 in FolderStorage::unGetMsg (this=0xb37f70, idx=0) at /build/buildd/kdepim-4.2.0/kmail/folderstorage.cpp:569
#38 0x00007f7d76740fe6 in KMSearchPattern::matches (this=0xade950, serNum=<value optimized out>, ignoreBody=<value optimized out>) at /build/buildd/kdepim-4.2.0/kmail/kmsearchpattern.cpp:794
#39 0x00007f7d766f6b99 in FolderStorage::slotProcessNextSearchBatch (this=0xb37f70) at /build/buildd/kdepim-4.2.0/kmail/folderstorage.cpp:1171
#40 0x00007f7d768ea2c6 in KMSearch::slotProcessNextBatch (this=0xad87f0) at /build/buildd/kdepim-4.2.0/kmail/kmfoldersearch.cpp:272
#41 0x00007f7d768ea438 in KMSearch::qt_metacall (this=0xad87f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7fb62340)
    at /build/buildd/kdepim-4.2.0/obj-x86_64-linux-gnu/kmail/kmfoldersearch.moc:78
#42 0x00007f7d73219134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#43 0x00007f7d73213a43 in QObject::event () from /usr/lib/libQtCore.so.4
#44 0x00007f7d73928c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#45 0x00007f7d739309ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#46 0x00007f7d775575db in KApplication::notify (this=0x7fff7fb62e50, receiver=0xadb150, event=0x7fff7fb629f0) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#47 0x00007f7d73204d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#48 0x00007f7d73230ab6 in ?? () from /usr/lib/libQtCore.so.4
#49 0x00007f7d7322d1fd in ?? () from /usr/lib/libQtCore.so.4
#50 0x00007f7d6a925d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#51 0x00007f7d6a92950d in ?? () from /usr/lib/libglib-2.0.so.0
#52 0x00007f7d6a9296cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#53 0x00007f7d7322d15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#54 0x00007f7d739baa6f in ?? () from /usr/lib/libQtGui.so.4
#55 0x00007f7d73203682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#56 0x00007f7d7320380d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#57 0x00007f7d73205cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#58 0x000000000040309b in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.0/kmail/main.cpp:146
Comment 18 Jaime Torres 2009-03-05 09:30:04 UTC
The backtraces of comment #12 and #13 are a duplicate of bug 184615
Last backtrace is new :-(.
Do you have any saved search? It looks like the search was being updated while you were composing the mail.
Comment 19 Jaime Torres 2009-03-05 09:45:32 UTC
*** Bug 186154 has been marked as a duplicate of this bug. ***
Comment 20 tony 2009-03-05 10:46:44 UTC
(In reply to comment #18)
> The backtraces of comment #12 and #13 are a duplicate of bug 184615
> Last backtrace is new :-(.
> Do you have any saved search? It looks like the search was being updated while
> you were composing the mail.

I assume you mean that there was a search that had results in the "searches" directory? If there's a particular way to save searches, I've never come across it (if there is, then it's POSSIBLE there's one there I don't know about.

If my assumption's right, then I don't THINK I had any, as I don't use searches very often. And the occasions when Kmail's crashed straight away after startup (getting worryingly regular now) I wouldn't expect anything saved

I wonder if the problem may be something in one particular saved message? I keep a couple of directories for classified spam and ham for spamassassin/bogofilter training. So they have a lot of emails in them and have long expiry times. Maybe whatever was originally causing this to keep happening expired, explaining the long gap since my original report, but another problematic one has since arrived.

I'll think about ways to move these two directories away from Kmail's structure to see if it helps.
Comment 21 Christophe Marin 2009-03-09 11:45:37 UTC
*** Bug 186422 has been marked as a duplicate of this bug. ***
Comment 22 Christophe Marin 2009-06-02 15:01:47 UTC
*** Bug 194990 has been marked as a duplicate of this bug. ***
Comment 23 Nikita Bige 2009-06-15 08:47:05 UTC
I get the same backtrace after update to 4.2.90 ( fedora 10 x86_64)
Comment 24 Christophe Marin 2009-07-12 17:50:42 UTC
*** Bug 199892 has been marked as a duplicate of this bug. ***
Comment 25 Constantin Berzan 2009-07-14 08:48:51 UTC
Reproduced comment #17 and filed bug 200137.
Comment 26 Christophe Marin 2009-08-03 08:31:55 UTC
this report has too many unrelated backtrace, which may lead to mistakes when triaging. Let's use bug 200137 as a reference instead.

*** This bug has been marked as a duplicate of bug 200137 ***