| Summary: | Crash when selecting gmail imap folder / listing a big IMAP folder (~ 65000 items) [KPIM::ProgressItem::setComplete, KMail::ImapAccountBase::removeJob, KMFolderImap::slotListFolderResult] | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Frederik Schwarzer <schwarzer> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | alex.merry, andresbajotierra, bjoern, herrfleisch, honkir, jensmh, jreidinger, jtamate, k0l0b0k.void, mail, mrdocs |
| Priority: | NOR | ||
| Version: | 1.10.90 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Frederik Schwarzer
2008-11-18 00:41:00 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.
> 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. 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... Possibly duplicate of bug 179765. The situation is similar but the backtrace is slightly different. *** Bug 198920 has been marked as a duplicate of this bug. *** *** Bug 209507 has been marked as a duplicate of this bug. *** 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 *** Bug 217977 has been marked as a duplicate of this bug. *** 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 *** Bug 218869 has been marked as a duplicate of this bug. *** Minor correction to comment #9: it is from bug 218869. Yeah, my bad. Thanks for fixing it. Created attachment 41366 [details]
New crash information added by DrKonqi
The problem is still 100% reproducible with Debian 4.4.1 experimental-snapshot packages.
*** This bug has been marked as a duplicate of bug 191345 *** *** Bug 262786 has been marked as a duplicate of this bug. *** *** Bug 264424 has been marked as a duplicate of this bug. *** *** Bug 265286 has been marked as a duplicate of this bug. *** *** Bug 270196 has been marked as a duplicate of this bug. *** |