Bug 220713 - Deleting too many items in KMail crashes program [DwEntity::*, KMMessage::headerField, KMail::FancyHeaderStyle::format, KMReaderWin::writeMsgHeader]
Summary: Deleting too many items in KMail crashes program [DwEntity::*, KMMessage::hea...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 198529 221103 222664 222888 224498 224663 224803 225923 226137 229254 231986 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-30 18:46 UTC by Shawn Starr
Modified: 2012-08-19 11:08 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.75 KB, text/plain)
2010-03-14 07:25 UTC, Lothar Werzinger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Starr 2009-12-30 18:46:31 UTC
Application: kmail (1.13.0)
KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) (Compiled from sources)
Qt Version: 4.6.1
Operating System: Linux 2.6.33-rc2-custom-radeon x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I was deleting a  a few emails rapidly (hold delete key) then Kmail crashes sometimes.

The crash can be reproduced some of the times.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f0f5d62868c in DwEntity::hasHeaders (this=0xf00000002fa7130) at /root/kdepim/mimelib/mimelib/entity.h:133
#6  0x00007f0f5d61e17c in KMMessage::headerField (this=0x24601e0, aName=..., encodingMode=KMMessage::MessageCharsetEncoding) at /root/kdepim/kmail/kmmessage.cpp:1949
#7  0x00007f0f5d8ab4a0 in KMail::FancyHeaderStyle::format (this=0x202d9e0, message=0x24601e0, strategy=0x1ca30b0, vCardName=..., printing=false, topLevel=true)
    at /root/kdepim/kmail/headerstyle.cpp:533
#8  0x00007f0f5d721e1f in KMReaderWin::writeMsgHeader (this=0x1b38b50, aMsg=0x24601e0, vCardNode=0x0, topLevel=true) at /root/kdepim/kmail/kmreaderwin.cpp:1724
#9  0x00007f0f5d720ab1 in KMReaderWin::parseMsg (this=0x1b38b50, aMsg=0x24601e0) at /root/kdepim/kmail/kmreaderwin.cpp:1605
#10 0x00007f0f5d720069 in KMReaderWin::displayMessage (this=0x1b38b50) at /root/kdepim/kmail/kmreaderwin.cpp:1534
#11 0x00007f0f5d71fb26 in KMReaderWin::updateReaderWin (this=0x1b38b50) at /root/kdepim/kmail/kmreaderwin.cpp:1477
#12 0x00007f0f5d72e5c6 in KMReaderWin::qt_metacall (this=0x1b38b50, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffcd80b400) at /root/kdepim-dev/kmail/kmreaderwin.moc:179
#13 0x00007f0f5a49d20d in QMetaObject::metacall (object=0x1b38b50, cl=QMetaObject::InvokeMetaMethod, idx=33, argv=0x7fffcd80b400) at /root/qt/src/corelib/kernel/qmetaobject.cpp:237
#14 0x00007f0f5a4b3601 in QMetaObject::activate (sender=0x1b38bf8, m=0x7f0f5a811e20, local_signal_index=0, argv=0x0) at /root/qt/src/corelib/kernel/qobject.cpp:3267
#15 0x00007f0f5a51af29 in QTimer::timeout (this=0x1b38bf8) at .moc/debug-shared/moc_qtimer.cpp:134
#16 0x00007f0f5a4bcd6b in QTimer::timerEvent (this=0x1b38bf8, e=0x7fffcd80be00) at /root/qt/src/corelib/kernel/qtimer.cpp:271
#17 0x00007f0f5a4aee33 in QObject::event (this=0x1b38bf8, e=0x7fffcd80be00) at /root/qt/src/corelib/kernel/qobject.cpp:1204
#18 0x00007f0f58d00818 in QApplicationPrivate::notify_helper (this=0x1b0f420, receiver=0x1b38bf8, e=0x7fffcd80be00) at /root/qt/src/gui/kernel/qapplication.cpp:4297
#19 0x00007f0f58cfdcb6 in QApplication::notify (this=0x7fffcd80c360, receiver=0x1b38bf8, e=0x7fffcd80be00) at /root/qt/src/gui/kernel/qapplication.cpp:3701
#20 0x00007f0f5e85ad37 in KApplication::notify (this=0x7fffcd80c360, receiver=0x1b38bf8, event=0x7fffcd80be00) at /root/kdelibs/kdeui/kernel/kapplication.cpp:302
#21 0x00007f0f5a4951b0 in QCoreApplication::notifyInternal (this=0x7fffcd80c360, receiver=0x1b38bf8, event=0x7fffcd80be00) at /root/qt/src/corelib/kernel/qcoreapplication.cpp:704
#22 0x00007f0f5a499135 in QCoreApplication::sendEvent (receiver=0x1b38bf8, event=0x7fffcd80be00) at ../../include/QtCore/../../../qt/src/corelib/kernel/qcoreapplication.h:215
#23 0x00007f0f5a4d5803 in QTimerInfoList::activateTimers (this=0x1b12d10) at /root/qt/src/corelib/kernel/qeventdispatcher_unix.cpp:603
#24 0x00007f0f5a4d0bb3 in timerSourceDispatch (source=0x1b12cb0) at /root/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:184
#25 0x00007f0f50abb8fe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00007f0f50abf2b8 in ?? () from /lib/libglib-2.0.so.0
#27 0x00007f0f50abf3e0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x00007f0f5a4d204b in QEventDispatcherGlib::processEvents (this=0x1accfe0, flags=...) at /root/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:412
#29 0x00007f0f58de6f94 in QGuiEventDispatcherGlib::processEvents (this=0x1accfe0, flags=...) at /root/qt/src/gui/kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007f0f5a4921a8 in QEventLoop::processEvents (this=0x7fffcd80c180, flags=...) at /root/qt/src/corelib/kernel/qeventloop.cpp:149
#31 0x00007f0f5a4922fe in QEventLoop::exec (this=0x7fffcd80c180, flags=...) at /root/qt/src/corelib/kernel/qeventloop.cpp:201
#32 0x00007f0f5a4958b2 in QCoreApplication::exec () at /root/qt/src/corelib/kernel/qcoreapplication.cpp:981
#33 0x00007f0f58cfd834 in QApplication::exec () at /root/qt/src/gui/kernel/qapplication.cpp:3576
#34 0x0000000000403c5d in main (argc=3, argv=0x7fffcd80c528) at /root/kdepim/kmail/main.cpp:156

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-03 15:46:48 UTC
This could be related to bug 198529. Thanks
Comment 2 Dario Andres 2010-01-31 01:12:05 UTC
From bug 221103:
-- Information about the crash:
When deleting Email in Kmail/Kontact using the delete key I suffer from this
crash, it seems easier to trigger on folders with 10 or more Emails or using
the delete key very fast. Selecting any number of messages with CTRL A and
using the delete key works fine. The crash can be reproduced everytime.

From bug 222664:
-- Information about the crash:
Application crashed while entering icorrectly entered password.

From bug 224803:
-- Information about the crash:
I executed "sudo swapoff -a" after waking the computer from hibernation to
clear the swap.
This resulted in the harddrive being *really* busy for a relatively long time.
While it was working, I deleted two spam mails in quick succession, using the
delete key.
Comment 3 Dario Andres 2010-01-31 01:12:14 UTC
*** Bug 221103 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-01-31 01:12:16 UTC
*** Bug 222664 has been marked as a duplicate of this bug. ***
Comment 5 Dario Andres 2010-01-31 01:12:19 UTC
*** Bug 222888 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2010-01-31 01:12:22 UTC
*** Bug 224803 has been marked as a duplicate of this bug. ***
Comment 7 Albert Astals Cid 2010-02-17 20:39:18 UTC
Just happened to me too, same backtrace
Comment 8 Martin Koller 2010-02-27 15:08:59 UTC
*** Bug 225923 has been marked as a duplicate of this bug. ***
Comment 9 Björn Ruberg 2010-03-14 01:46:11 UTC
*** Bug 229254 has been marked as a duplicate of this bug. ***
Comment 10 Lothar Werzinger 2010-03-14 07:25:57 UTC
Created attachment 41615 [details]
New crash information added by DrKonqi

crashed kontact when deleted two mails while the system was busy
Comment 11 Björn Ruberg 2010-03-14 21:16:37 UTC
*** Bug 198529 has been marked as a duplicate of this bug. ***
Comment 12 Christophe Marin 2010-03-26 00:41:05 UTC
*** Bug 231986 has been marked as a duplicate of this bug. ***
Comment 13 Christophe Marin 2010-03-27 21:49:47 UTC
*** Bug 226137 has been marked as a duplicate of this bug. ***
Comment 14 Christophe Marin 2010-03-28 00:11:26 UTC
*** Bug 224663 has been marked as a duplicate of this bug. ***
Comment 15 Björn Ruberg 2010-04-02 13:18:25 UTC
*** Bug 224498 has been marked as a duplicate of this bug. ***
Comment 16 Björn Ruberg 2010-04-02 13:18:59 UTC
*** Bug 232191 has been marked as a duplicate of this bug. ***
Comment 17 Myriam Schweingruber 2012-08-19 11:08:39 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding