Bug 175452 - Crash when selecting gmail imap folder / listing a big IMAP folder (~ 65000 items) [KPIM::ProgressItem::setComplete, KMail::ImapAccountBase::removeJob, KMFolderImap::slotListFolderResult]
Summary: Crash when selecting gmail imap folder / listing a big IMAP folder (~ 65000 i...
Status: RESOLVED DUPLICATE of bug 191345
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: 1.10.90
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 198920 209507 217977 218869 262786 264424 265286 270196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-18 00:41 UTC by Frederik Schwarzer
Modified: 2011-04-06 15:28 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (5.12 KB, text/plain)
2010-03-05 21:49 UTC, jensmh 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Frederik Schwarzer 2008-11-18 00:41:00 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

When I selected the gmail imap folder, KMail crashed with the attached backtrace.
This is not clearly reproducable for me (happend two times tonight, in about three dozens of tries), I hope the bt helps anyway.


Application: KMail (kmail), Signal SIGSEGV

Thread 1 (Thread 0xb3dd7740 (LWP 12961)):
[KCrash Handler]
#6  KPIM::ProgressItem::setComplete (this=0x20006d) at /home/compiler/kde/src/KDE/kdepim/libkdepim/progressmanager.cpp:53
#7  0xb74a7c7b in KMail::ImapAccountBase::removeJob (this=0x82bc3b0, it=@0xbff14a9c) at /home/compiler/kde/src/KDE/kdepim/kmail/imapaccountbase.cpp:1363
#8  0xb74e3fb6 in KMFolderImap::slotListFolderResult (this=0x8269020, job=0x8a69b10) at /home/compiler/kde/src/KDE/kdepim/kmail/kmfolderimap.cpp:1312
#9  0xb74e72bc in KMFolderImap::qt_metacall (this=0x8269020, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbff14bcc) at /home/compiler/kde/build/KDE/kdepim/kmail/kmfolderimap.moc:181
#10 0xb573fbd0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb5740952 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7b06533 in KJob::result (this=0x8a69b10, _t1=0x8a69b10) at /home/compiler/kde/build/KDE/kdelibs/kdecore/kjob.moc:186
#13 0xb7b06a49 in KJob::emitResult (this=0x8a69b10) at /home/compiler/kde/src/KDE/kdelibs/kdecore/jobs/kjob.cpp:294
#14 0xb5994105 in KIO::SimpleJob::slotFinished (this=0x8a69b10) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job.cpp:489
#15 0xb59970fe in KIO::ListJob::slotFinished (this=0x8a69b10) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job.cpp:2416
#16 0xb5991933 in KIO::SimpleJob::slotError (this=0x8a69b10, err=149, errorText=@0xbff14fb0) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job.cpp:501
#17 0xb5991b2b in KIO::SimpleJob::qt_metacall (this=0x8a69b10, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff14e68) at /home/compiler/kde/build/KDE/kdelibs/kio/jobclasses.moc:155
#18 0xb599912a in KIO::ListJob::qt_metacall (this=0x8a69b10, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbff14e68) at /home/compiler/kde/build/KDE/kdelibs/kio/jobclasses.moc:739
#19 0xb573fbd0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb5740952 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#21 0xb5a5e719 in KIO::SlaveInterface::error (this=0x8067150, _t1=149, _t2=@0xbff14fb0) at /home/compiler/kde/build/KDE/kdelibs/kio/slaveinterface.moc:151
#22 0xb5a62577 in KIO::SlaveInterface::dispatch (this=0x8067150, _cmd=102, rawdata=@0xbff14ff4) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:208
#23 0xb5a5eb6d in KIO::SlaveInterface::dispatch (this=0x8067150) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:91
#24 0xb5a4ff2d in KIO::Slave::gotInput (this=0x8067150) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/slave.cpp:322
#25 0xb5a510a3 in KIO::Slave::qt_metacall (this=0x8067150, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff15108) at /home/compiler/kde/build/KDE/kdelibs/kio/slave.moc:75
#26 0xb573fbd0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#27 0xb5740952 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#28 0xb5958d77 in KIO::Connection::readyRead (this=0x86167e0) at /home/compiler/kde/build/KDE/kdelibs/kio/connection.moc:84
#29 0xb595ae39 in KIO::ConnectionPrivate::dequeue (this=0x86195d8) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/connection.cpp:82
#30 0xb595afc6 in KIO::Connection::qt_metacall (this=0x86167e0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x89b03a8) at /home/compiler/kde/build/KDE/kdelibs/kio/connection.moc:72
#31 0xb5738d6b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#32 0xb573a8e1 in QObject::event () from /usr/lib/libQtCore.so.4
#33 0xb4d2079c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#34 0xb4d2861e in QApplication::notify () from /usr/lib/libQtGui.so.4
#35 0xb7e3dc0d in KApplication::notify (this=0xbff15a08, receiver=0x86167e0, event=0x881c7d0) at /home/compiler/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#36 0xb572b0d1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#37 0xb572bd55 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#38 0xb572bf4d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#39 0xb4dbae3f in ?? () from /usr/lib/libQtGui.so.4
#40 0xb572979a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#41 0xb572995a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#42 0xb572c015 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#43 0xb4d20617 in QApplication::exec () from /usr/lib/libQtGui.so.4
#44 0x0804a980 in main (argc=137086824, argv=0xb5810128) at /home/compiler/kde/src/KDE/kdepim/kmail/main.cpp:146
Comment 1 Jaime Torres 2008-11-19 16:21:04 UTC 
I've just checked libkdepim/progressmanager.cpp and it reads

if ( mChildren.isEmpty() ) {

but mChildren, if I'm not mixing Java and C++, declared as a private variable is  not initialized in the constructor.
Comment 2 Thomas McGuire 2008-11-19 19:23:52 UTC 
> I've just checked libkdepim/progressmanager.cpp and it reads

> if ( mChildren.isEmpty() ) {

>but mChildren, if I'm not mixing Java and C++, declared as a private variable is  not initialized in the constructor.

mChildren is a QMap, which is automatically constructed with the default QMap constructor. The real problem is that this=0x20006d, i.e. the pointer to the progressitem is invalid, probably because the jobData is invalid.

Anyway, I can't reproduce this problem, it looks like this only happens when listing a folder gets an error.
Maybe running KMail through valgrind would get a useful result.
Comment 3 Frederik Schwarzer 2008-12-02 18:41:27 UTC 
I do not know, if you see something from the backtrace...
I only want to let you know that I wasn't able to reproduce this since then...
Comment 4 George Kiagiadakis 2009-01-13 16:07:34 UTC 
Possibly duplicate of bug 179765. The situation is similar but the backtrace is slightly different.
Comment 5 Christophe Marin 2009-07-05 13:26:39 UTC 
*** Bug 198920 has been marked as a duplicate of this bug. ***
Comment 6 Christophe Marin 2009-10-05 13:14:17 UTC 
*** Bug 209507 has been marked as a duplicate of this bug. ***
Comment 7 Dario Andres 2009-12-10 16:36:15 UTC 
From bug 217977:
---
What I was doing when the application crashed:
My internet connection lag (disconnect for a minute) and kontact show error
window. After showing this error window it crashes. ( I don't remember what
wxactly is in error window, but it is something about timeout exceed).

Thread 1 (Thread 0x7f5c5d38d750 (LWP 32749)):
[KCrash Handler]
#5  0x00007f5c5cb10b61 in KPIM::ProgressItem::setComplete() () from
/usr/lib64/libkdepim.so.4
#6  0x00007f5c464b7495 in KMail::ImapAccountBase::removeJob (this=0xb3fda0,
it=...) at /usr/src/debug/kdepim-4.3.3/kmail/imapaccountbase.cpp:1370
#7  0x00007f5c464db69a in KMFolderImap::slotListFolderResult (this=0xbc8570,
job=0xdf4230) at /usr/src/debug/kdepim-4.3.3/kmail/kmfolderimap.cpp:1314
#8  0x00007f5c464e74b5 in KMFolderImap::qt_metacall (this=0xbc8570,
_c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff0f5d6e10) at
/usr/src/debug/kdepim-4.3.3/build/kmail/kmfolderimap.moc:182
Comment 8 Dario Andres 2009-12-10 16:36:19 UTC 
*** Bug 217977 has been marked as a duplicate of this bug. ***
Comment 9 Dario Andres 2009-12-17 01:00:14 UTC 
From bug 175452 (which contains several bits of useful information):
---
I can reproduce this crash 100% when accessing folders with 64000+ messages.  (courier-imap server running on Debian Lenny)
With smaller folders (25000 or less messages) no crash.

Updated (4.4trunk) backtrace:
---
#5  KPIM::ProgressItem::setComplete (this=0x6c64657463657078) at
/home/jmho/kde-devel/kdesvn/kdepim/libkdepim/progressmanager.cpp:52
#6  0x00007f2ba9879f65 in KMail::ImapAccountBase::removeJob (this=0x1e2f9f0,
it=...) at /home/jmho/kde-devel/kdesvn/kdepim/kmail/imapaccountbase.cpp:1375
#7  0x00007f2ba98a4036 in KMFolderImap::slotListFolderResult (this=0x28970a0,
job=<value optimized out>) at
/home/jmho/kde-devel/kdesvn/kdepim/kmail/kmfolderimap.cpp:1305
#8  0x00007f2ba98aae25 in KMFolderImap::qt_metacall (this=0x28970a0,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe44dbfd0)
    at /home/jmho/kde-devel/kdesvn/build/kdepim/kmail/kmfolderimap.moc:188
Comment 10 Dario Andres 2009-12-17 01:00:28 UTC 
*** Bug 218869 has been marked as a duplicate of this bug. ***
Comment 11 jensmh 2009-12-17 01:35:11 UTC 
Minor correction to comment #9: it is from bug 218869.
Comment 12 Dario Andres 2009-12-17 01:38:52 UTC 
Yeah, my bad. Thanks for fixing it.
Comment 13 jensmh 2010-03-05 21:49:54 UTC 
Created attachment 41366 [details]
New crash information added by DrKonqi

The problem is still 100% reproducible with Debian 4.4.1 experimental-snapshot packages.
Comment 14 Björn Ruberg 2010-08-06 00:50:02 UTC 

*** This bug has been marked as a duplicate of bug 191345 ***
Comment 15 Christophe Marin 2011-01-10 23:35:31 UTC 
*** Bug 262786 has been marked as a duplicate of this bug. ***
Comment 16 Christophe Marin 2011-01-27 11:22:14 UTC 
*** Bug 264424 has been marked as a duplicate of this bug. ***
Comment 17 Christophe Marin 2011-02-03 14:31:13 UTC 
*** Bug 265286 has been marked as a duplicate of this bug. ***
Comment 18 Christophe Marin 2011-04-06 15:28:45 UTC 
*** Bug 270196 has been marked as a duplicate of this bug. ***