Bug 185423

Summary: Frequent crashes after compacting folders (mbox)
Product: [Applications] kmail Reporter: A. Pfaller <apfaller>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, christophe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: backtrace

Description A. Pfaller 2009-02-24 10:21:41 UTC
Version:            (using KDE 4.2.0)
Compiler:          gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) as shipped with OpenSUSE 11.0
OS:                Linux
Installed from:    Compiled From Sources

After compating a mbox folder kmail (4.2 svn branch, rev. 930780) frequently crashes.
Comment 1 A. Pfaller 2009-02-24 10:23:35 UTC
Created attachment 31593 [details]
backtrace

backtrace of crash shortly after selecting 
"compact folder" for trash folder.
Comment 2 Dario Andres 2009-02-24 23:22:51 UTC
Pasted backtrace from comment 1:

Application: KMail (kmail), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
0x00007fb58c64b1f0 in nanosleep () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb591c1c700 (LWP 8646)):
[KCrash Handler]
#5  KMail::MessageListView::Core::Model::index (this=0x7797d00, item=0x80986b0, column=0) at /mnt/l0/x64/svn-kde/branches/KDE/4.2/kdepim/kmail/messagelistview/core/item.h:284
#6  0x00007fb590b73e9b in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x7797d00) at /mnt/l0/x64/svn-kde/branches/KDE/4.2/kdepim/kmail/messagelistview/core/model.cpp:3813
#7  0x00007fb59071ead8 in KMail::MessageListView::Core::Model::qt_metacall (this=0x7797d00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff99c7f910)
    at /mnt/l0/x64/svn-kde/branches/KDE/4.2/kdepim/build/kmail/moc_model.cpp:75
#8  0x00007fb58e451954 in QMetaObject::activate (sender=0x77d4110, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#9  0x00007fb58e44c283 in QObject::event (this=0x77d4110, e=0x7797d00) at kernel/qobject.cpp:1120
#10 0x00007fb58d21210d in QApplicationPrivate::notify_helper (this=0x63ae20, receiver=0x77d4110, e=0x7fff99c80010) at kernel/qapplication.cpp:3803
#11 0x00007fb58d219eba in QApplication::notify (this=0x7fff99c80520, receiver=0x77d4110, e=0x7fff99c80010) at kernel/qapplication.cpp:3768
#12 0x00007fb59168288b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#13 0x00007fb58e43d5d1 in QCoreApplication::notifyInternal (this=0x7fff99c80520, receiver=0x77d4110, event=0x7fff99c80010) at kernel/qcoreapplication.cpp:587
#14 0x00007fb58e469760 in QTimerInfoList::activateTimers (this=0x63d300) at kernel/qcoreapplication.h:209
#15 0x00007fb58e465b1d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:160
#16 0x00007fb583abe93a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007fb583ac2040 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fb583ac21dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fb58e465a7f in QEventDispatcherGlib::processEvents (this=0x6288b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#20 0x00007fb58d2a284f in QGuiEventDispatcherGlib::processEvents (this=0x7fff99c7f700, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198
#21 0x00007fb58e43bed2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1714945232}) at kernel/qeventloop.cpp:143
#22 0x00007fb58e43c05d in QEventLoop::exec (this=0x7fff99c80370, flags={i = -1714945152}) at kernel/qeventloop.cpp:194
#23 0x00007fb58e43e54d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#24 0x00000000004030db in main (argc=<value optimized out>, argv=<value optimized out>) at /mnt/l0/x64/svn-kde/branches/KDE/4.2/kdepim/kmail/main.cpp:146
Comment 3 Dario Andres 2009-02-24 23:23:24 UTC
This is probably related to bug 181934 as the backtrace seems to be the same
Comment 4 Christophe Marin 2009-03-09 10:27:20 UTC

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