Bug 204107

*** Bug 203489 has been marked as a duplicate of this bug. ***

Kmail crashed here - kde 4.3 branch, recently (as of this post) synced from svn, from Gentoo live packages (so no dirty-build-dir issues), Qt-4.5.1, using IMAP.

Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007ffa0abd7720 in QListData::shared_null () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007ffa04ac073b in qDeleteAll<QList<KIO::Slave*>::const_iterator> (begin=..., end=...) at /usr/include/qt4/QtCore/qalgorithms.h:350
#7  0x00007ffa04ac1119 in qDeleteAll<SlaveList> (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:358
#8  0x00007ffa04ac1d56 in KIO::SchedulerPrivate::ProtocolInfo::~ProtocolInfo (this=0x171c370, __in_chrg=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.9999/work/kdelibs-4.3.9999/kio/kio/scheduler.cpp:171
#9  0x00007ffa04ac1ddd in qDeleteAll<QHash<QString, KIO::SchedulerPrivate::ProtocolInfo*>::const_iterator> (begin=..., end=...) at /usr/include/qt4/QtCore/qalgorithms.h:350
#10 0x00007ffa04ac1e2f in qDeleteAll<KIO::SchedulerPrivate::ProtocolInfoDict> (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:358
#11 0x00007ffa04ac2068 in KIO::SchedulerPrivate::~SchedulerPrivate (this=0x1283500, __in_chrg=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.9999/work/kdelibs-4.3.9999/kio/kio/scheduler.cpp:103
#12 0x00007ffa04abc511 in <anonymous struct>::destroy(void) () at /var/tmp/portage/kde-base/kdelibs-4.3.9999/work/kdelibs-4.3.9999/kio/kio/scheduler.cpp:209
#13 0x00007ffa04a15571 in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0x7ffa04df7c58, __in_chrg=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.9999/work/kdelibs-4.3.9999/kdecore/kernel/kglobal.h:62
#14 0x00007ffa09f926fd in exit () from /lib/libc.so.6
#15 0x00007ffa09f7a5cd in __libc_start_main () from /lib/libc.so.6
#16 0x00000000004024d9 in _start ()

Kmail crashed on exit that is.

@Maciej Mrozowski: the crash you posted is a different one already reported. Thanks

Some scenario but indeed backtrace is different - separate bug report then?

@Maciej: your crash is already reported at bug 199375. Thanks!

*** Bug 207541 has been marked as a duplicate of this bug. ***

*** Bug 212036 has been marked as a duplicate of this bug. ***

*** Bug 212578 has been marked as a duplicate of this bug. ***

*** Bug 214236 has been marked as a duplicate of this bug. ***

From bug 214329:
---
What I was doing when the application crashed:
After starting kmail i have heavy harddisk activity, i think kmail try to
reindexing all emails. In my lokal Mail-Folders i have over 11GB mails, so
kmail needs >30min for indexing. If I had not the time to wait, i try to close
kmail and than it crashed sometimes doing this.
---

Backtrace:
---

Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  QBasicAtomicInt::operator!= (this=0x3e1ab40, job=0x3e38610) at
/usr/include/qt4/QtCore/qbasicatomic.h:69
#6  QMap<KJob*, KMail::ImapAccountBase::jobData>::detach (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:172
#7  QMap<KJob*, KMail::ImapAccountBase::jobData>::find (this=0x3e1ab40,
job=0x3e38610) at /usr/include/qt4/QtCore/qmap.h:565
#8  KMail::ImapAccountBase::findJob (this=0x3e1ab40, job=0x3e38610) at
../../kmail/imapaccountbase.h:180
#9  KMail::ListJob::slotListResult (this=0x3e1ab40, job=0x3e38610) at
../../kmail/listjob.cpp:166
#10 0x00007f9ab9689c53 in KMail::ListJob::qt_metacall (this=0x3e1ab40,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff3e9f36d0)
at ./listjob.moc:77

*** Bug 214329 has been marked as a duplicate of this bug. ***

From bug 215085, a more complete backtrace:
----
Thread 1 (Thread 0xb77d5700 (LWP 3244)):
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0xa061450, job=0xa062260, uds=...) at
/usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QString (this=0xa061450, job=0xa062260, uds=...) at
/usr/include/qt4/QtCore/qstring.h:712
#8  jobData (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/imapaccountbase.h:146
#9  QMap<KJob*, KMail::ImapAccountBase::jobData>::node_create (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:421
#10 QMap<KJob*, KMail::ImapAccountBase::jobData>::detach_helper
(this=0xa061450, job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:708
#11 QMap<KJob*, KMail::ImapAccountBase::jobData>::detach (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:172
#12 QMap<KJob*, KMail::ImapAccountBase::jobData>::find (this=0xa061450,
job=0xa062260, uds=...) at /usr/include/qt4/QtCore/qmap.h:565
#13 KMail::ImapAccountBase::findJob (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/imapaccountbase.h:180
#14 KMail::ListJob::slotListEntries (this=0xa061450, job=0xa062260, uds=...) at
../../kmail/listjob.cpp:189
#15 0xb436ff86 in KMail::ListJob::qt_metacall (this=0xa061450,
_c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfe17494) at ./listjob.moc:78
#16 0x0717d263 in QMetaObject::activate (sender=0xa062260,
from_signal_index=40, to_signal_index=40, argv=0xbfe17494) at
kernel/qobject.cpp:3113
#17 0x0717dec2 in QMetaObject::activate (sender=0xa062260, m=0x3e9d3a0,
local_signal_index=0, argv=0xbfe17494) at kernel/qobject.cpp:3187
#18 0x03ce53a9 in KIO::ListJob::entries (this=0xa062260, _t1=0xa062260,
_t2=...) at ./jobclasses.moc:781
#19 0x03cf40ab in KIO::ListJobPrivate::slotListEntries (this=0xa061eb8,
list=...) at ../../kio/kio/job.cpp:2333
#20 0x03cf4458 in KIO::ListJob::qt_metacall (this=0xa062260,
_c=QMetaObject::InvokeMetaMethod, _id=46, _a=0xbfe17698) at
./jobclasses.moc:767
...

*** Bug 215085 has been marked as a duplicate of this bug. ***

*** Bug 219657 has been marked as a duplicate of this bug. ***

I can confirm this bug. I reported it as bug #220361. I was not sure whether it is a duplicate as for me it does not roughly happen once a day, but on reproducable conditions:

1) kontact crashes on quitting it *shortly* after starting it.
2) it does so when kmail part is being the one displayed initially, it doesn't crash when the summary page is being displayed instead.
3) it doesn't crash here when I wait a few seconds.
4) kmail started alone doesn't crash when quitting it shortly after starting.

*** Bug 220361 has been marked as a duplicate of this bug. ***

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