Bug 180886

Summary: KMail 1.11.0 (KDE-4.1.96) crashes when deleting multiple messages
Product: [Unmaintained] kmail Reporter: Kenjiro Tanaka <jedi.kenjiro>
Component: new message listAssignee: Szymon Stefanek <pragma>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, christophe, m.wege, Tanktalus
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Kenjiro Tanaka 2009-01-15 22:14:18 UTC
Version:           1.11.0 (KDE-4.1.96) (using Devel)
Compiler:          gcc-4.2.4 
OS:                Linux
Installed from:    Compiled sources

It is the second time it happens. When I delete multiple messages at once, KMail crashes.

Bellow is the crash message:

#####
Application: Kontact (kontact), signal SIGABRT
0x00007f3683fd93f1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 2252)]

Thread 2 (Thread 0x41953950 (LWP 1808)):
#0  0x00007f368400b292 in select () from /lib/libc.so.6
#1  0x00007f3685de90a5 in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007f3685d26c22 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f3685aac38b in start_thread () from /lib/libpthread.so.0
#4  0x00007f3684011ced in clone () from /lib/libc.so.6

Thread 1 (Thread 0x7f368a5d0700 (LWP 2252)):
[KCrash Handler]
#5  0x00007f3683f6df05 in raise () from /lib/libc.so.6
#6  0x00007f3683f6f960 in abort () from /lib/libc.so.6
#7  0x00007f3685d1ed65 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f3685d1eea7 in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f3672687c48 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x00007f367268bb1a in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x00007f367268c536 in ?? () from /usr/lib/libkmailprivate.so.4
#12 0x00007f367268d314 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0x00007f36721ec60e in ?? () from /usr/lib/libkmailprivate.so.4
#14 0x00007f3685e1c426 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0x00007f3685e16d35 in QObject::event () from /usr/lib/libQtCore.so.4
#16 0x00007f3684bdc48f in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#17 0x00007f3684bde645 in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0x00007f3686c6635b in KApplication::notify () from /usr/lib/libkdeui.so.5
#19 0x00007f3685e08299 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#20 0x00007f3685e334cc in ?? () from /usr/lib/libQtCore.so.4
#21 0x00007f3685e3103d in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f367ff259c4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007f367ff28cc5 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f367ff291ab in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007f3685e3149f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f3684c6505f in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007f3685e07715 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0x00007f3685e0786b in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0x00007f3685e098b9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0x00000000004045da in _start ()

#####

At least the messages are really deleted ;)
Comment 1 Dario Andres 2009-01-15 22:42:51 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Kenjiro Tanaka 2009-01-16 19:03:15 UTC
Well, after I enabled "debugfull" in all my kde packages, plasma crashes EVERYTIME I start KDE. So I will have to go back to the "without debugfull" packages :(
Comment 3 Darin McBride 2009-01-16 19:21:00 UTC
I think this is the same problem that I'm getting.  Here's a more full trace:


Thread 1 (Thread 0x7ffd562d8700 (LWP 18123)):
#0  0x00007ffd4f65c3c5 in raise () from /lib/libc.so.6
No symbol table info available.
#1  0x00007ffd4f65d73e in abort () from /lib/libc.so.6
No symbol table info available.
#2  0x00007ffd5036e9e5 in qt_message_output ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#3  0x00007ffd5036eb17 in qFatal () from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#4  0x00007ffd3f2acabe in KMail::MessageListView::Core::Model::viewItemJobStep
    (this=0xf5d470)
    at /var/tmp/portage/kde-base/kmail-4.1.96/work/kmail-4.1.96/kmail/messagelistview/core/model.cpp:3778
	stillIgnoringCurrentChanges = <value optimized out>
	currentIndexAfterStep = {r = 0, c = 0, p = 0x7ffd4f69cc82, m = 0x39}
	currentAfterStep = <value optimized out>
	rectAfterViewItemJobStep = {x1 = 15983904, y1 = 0, x2 = 1347042816, 
  y2 = 32765}
	currentIndexBeforeStep = {r = 0, c = 0, p = 0x1203f80, m = 0xf5d470}
	currentItemBeforeStep = (class KMail::MessageListView::Core::Item
     *) 0x1203f80
	rectBeforeViewItemJobStep = {x1 = 0, y1 = 0, x2 = 1064, y2 = 26}
	__PRETTY_FUNCTION__ = "void KMail::MessageListView::Core::Model::viewItemJobStep()"
#5  0x00007ffd3efbd6df in KMail::MessageListView::Core::Model::qt_metacall (
    this=0xf5d470, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff5e32b1a0)
    at /var/tmp/portage/kde-base/kmail-4.1.96/work/kmail_build/kmail/moc_model.cpp:75
No locals.
#6  0x00007ffd504c5fd1 in QMetaObject::activate ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#7  0x00007ffd504c2a12 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#8  0x00007ffd50ff8a7e in QApplicationPrivate::notify_helper ()
   from /usr/lib64/qt4/libQtGui.so.4
No symbol table info available.
#9  0x00007ffd50ff8b9e in QApplication::notify ()
   from /usr/lib64/qt4/libQtGui.so.4
No symbol table info available.
#10 0x00007ffd523e9f61 in KApplication::notify (this=0x7fff5e32bd40, 
    receiver=0xf5d3a0, event=0x7fff5e32b7e0)
    at /var/tmp/portage/kde-base/kdelibs-4.1.96/work/kdelibs-4.1.96/kdeui/kernel/kapplication.cpp:307
	t = QEvent::None
#11 0x00007ffd504af2a8 in QCoreApplication::notifyInternal ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#12 0x00007ffd504e29b1 in ?? () from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#13 0x00007ffd504e2d30 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#14 0x00007ffd5108ab6b in QEventDispatcherX11::processEvents ()
   from /usr/lib64/qt4/libQtGui.so.4
No symbol table info available.
#15 0x00007ffd504ae815 in QEventLoop::processEvents ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#16 0x00007ffd504ae8f5 in QEventLoop::exec ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#17 0x00007ffd504b0a8e in QCoreApplication::exec ()
   from /usr/lib64/qt4/libQtCore.so.4
No symbol table info available.
#18 0x0000000000404138 in main (argc=1, argv=0x7fff5e32c268)
    at /var/tmp/portage/kde-base/kontact-4.1.96/work/kontact-4.1.96/kontact/src/main.cpp:218
	about = {d = 0x8ba3b0}
	args = <value optimized out>
	app = {<KUniqueApplication> = {<KApplication> = {<> = {<No data fields>}, static staticMetaObject = {d = {superdata = 0x7ffd519fa200, 
          stringdata = 0x7ffd52511d40 "KApplication", data = 0x7ffd52511ee0, 
          extradata = 0x0}}, static loadedByKdeinit = false, 
      static KApp = 0x7fff5e32bd40, d = 0x922cc0}, static staticMetaObject = {
      d = {superdata = 0x7ffd527b88a0, 
        stringdata = 0x7ffd52512540 "KUniqueApplication", 
        data = 0x7ffd52512640, extradata = 0x0}}, d = 0x95b630}, 
  static staticMetaObject = {d = {superdata = 0x6074e0, 
      stringdata = 0x4052e0 "KontactApp", data = 0x4053a0, extradata = 0x0}}, 
  mMainWindow = 0x9c5e00, mSessionRestored = false}
#19 0x00007ffd4f649b74 in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#20 0x0000000000403379 in _start ()
No symbol table info available.
The program is running.  Quit anyway (and detach it)? (y or n) Detaching from program: /usr/kde/4.2/bin/kontact, process 18123

Note that I get this every time I try to empty my trash.  I "open" each of the four groups ("January 2010", "Tuesday", "Monday", and "Last Week"), and then right-click on trash.  Then I select "Empty trash".  And crash.  I attached gdb to kontact last time, and got the above backtrace.  I don't actually have debugging versions of the libraries - they're stripped out and the debug files are in /usr/debug or something.  (I've told Gentoo to do this automatically.  Speed AND good backtraces.)  Oddly, DrKonqi isn't coming up.

I'm running KDE 4.1.96 at the moment.
Comment 4 Dario Andres 2009-01-16 19:21:58 UTC
@Kenjiro: if Plasma crashes too, file a bug report for Plasma :)
Comment 5 Dario Andres 2009-01-16 19:27:09 UTC
@Darin: your backtrace looks like the one in bug 174839. That bug may be related to this original or report (or not).
Comment 6 Kenjiro Tanaka 2009-01-16 20:59:55 UTC
@Darío: The "problem" is quite like that reported on bug 174839.

Plasma wasn't crashing on me until I enabled "debugfull" on all my KDE packages. I tried disabling that on kdebase-workspace and kdebase, but that didn't solve the plasma problem. So I disabled debugfull in kdelibs too, now I got my Plasma working again, but sure, I can't help you guys with the backtrace :( 

Really sorry.
Comment 7 Ava Greve 2009-02-09 15:17:57 UTC
Hello, all,

Thank you very much for the great work you are doing! I migrated recently to KDE and I love it. 

I am using KDE 4.2 and I also have an experience of  regular crashes of the Kmail, when I am deleting multiple messages. 
Although, I have observed a bit the behaviour and I noticed the following patterns:

Kmail crashes every time, when I am deleting multiple messages, but not  if they are 6-7 for example. The backtrace report below has been produced by my attempt to delete 17 messages. 

There is an interesting way to avoid crashes, I have discovered:

If I am NOT positioned in the “Deleted items” folder itself when I am deleting, but for example into the “Inbox”, and I am just using “right click” => “Empty Deleted items” I have no problems with the application. 

Warm regards,
Ava


Backtrace: 

Application: Kontact (kontact), signal SIGABRT
[Current thread is 0 (LWP 6021)]
Thread 2 (Thread 0xb0187b90 (LWP 6317)):
#0 0xb804c430 in __kernel_vsyscall ()
#1 0xb5ac8c01 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5d97150 in ?? () from /usr/lib/libQtCore.so.4
#3 0xb5cc76ae in ?? () from /usr/lib/libQtCore.so.4
#4 0xb53fe50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb5ad07ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb4b796c0 (LWP 6021)):
[KCrash Handler]
#6 0xb804c430 in __kernel_vsyscall ()
#7 0xb5a1a880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb5a1c248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb5cbf795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb5cbf872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb5cbf915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb17083c6 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0xb170b196 in ?? () from /usr/lib/libkmailprivate.so.4
#14 0xb170b74c in ?? () from /usr/lib/libkmailprivate.so.4
#15 0xb170c8c9 in ?? () from /usr/lib/libkmailprivate.so.4
#16 0xb125e903 in ?? () from /usr/lib/libkmailprivate.so.4
#17 0xb5dcca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb5dcd7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb5e077a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#20 0xb5dd340e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#21 0xb5dc753f in QObject::event () from /usr/lib/libQtCore.so.4
#22 0xb62698ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#23 0xb627172e in QApplication::notify () from /usr/lib/libQtGui.so.4
#24 0xb6d82fed in KApplication::notify () from /usr/lib/libkdeui.so.5
#25 0xb5db7e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#26 0xb5de5d81 in ?? () from /usr/lib/libQtCore.so.4
#27 0xb5de2520 in ?? () from /usr/lib/libQtCore.so.4
#28 0xb50906f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5093da3 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb5093f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb5de2478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb6303ea5 in ?? () from /usr/lib/libQtGui.so.4
#33 0xb5db652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#34 0xb5db66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#35 0xb5db8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#36 0xb6269767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#37 0x0804c072 in _start ()

Comment 8 Dario Andres 2009-02-09 21:46:35 UTC
@Ava: you need to install some packages in order to obtain a complete backtrace. Assumming you are using Kubuntu, can you install "kdepim-dbg" ?, then try to reproduce the crash (or when you eventually experience it), you will get a better backtrace. Finally you can compare it with the backtraces in this report. 
If you aren't sure that it's the same backtrace, attach the backtrace file in this report and I will check for it. Thanks
Comment 9 Ava Greve 2009-02-12 20:26:12 UTC
@ Dario

This time I needed some time to crash it again, it works much more stable.
I have installed the "kdepim-dbg" packages and here is the backtrace below. I don't know how to read the backtraces, so I guess you have to do that.

Thank you very much!

Application: Kontact (kontact), signal SIGABRT
[Current thread is 0 (LWP 6609)]
Thread 2 (Thread 0xb017eb90 (LWP 25342)):
#0 0xb8017430 in __kernel_vsyscall ()
#1 0xb5a93df1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5d62150 in ?? () from /usr/lib/libQtCore.so.4
#3 0xb5c926ae in ?? () from /usr/lib/libQtCore.so.4
#4 0xb53c950f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb5a9ba0e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb4b446c0 (LWP 6609)):
[KCrash Handler]
#6 0xb8017430 in __kernel_vsyscall ()
#7 0xb59e58a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb59e7268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb5c8a795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb5c8a872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb5c8a915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb169f949 in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x9a5f428) at /build/buildd/kdepim-4.2.0/kmail/messagelistview/core/model.cpp:3788
#13 0xb11f1903 in KMail::MessageListView::Core::Model::qt_metacall (this=0x9a5f428, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb16af8)
at /build/buildd/kdepim-4.2.0/obj-i486-linux-gnu/kmail/moc_model.cpp:75
#14 0xb5d97a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb5d987e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb5dd27a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#17 0xb5d9e40e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#18 0xb5d9253f in QObject::event () from /usr/lib/libQtCore.so.4
#19 0xb62348ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#20 0xb623c72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb6d4dfed in KApplication::notify (this=0xbfb17238, receiver=0x9a5f3f0, event=0xbfb16f8c) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#22 0xb5d82e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#23 0xb5db0d81 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb5dad520 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb505b6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb505eda3 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb505ef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb5dad478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb62ceea5 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb5d8152a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#31 0xb5d816ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#32 0xb5d83da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#33 0xb6234767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#34 0x0804c072 in main (argc=1, argv=0xbfb17534) at /build/buildd/kdepim-4.2.0/kontact/src/main.cpp:218

Comment 10 Jaime Torres 2009-02-12 21:00:25 UTC
*** Bug 182260 has been marked as a duplicate of this bug. ***
Comment 11 Dario Andres 2009-02-12 21:39:46 UTC
@Ava: your crash is indeed the same as the one in comment 3 (however, I'm not sure if both of them are related to the original report)
Comment 12 Dario Andres 2009-08-02 01:12:53 UTC
Ok, let's assume the original report was indeed related to bug 174839.

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