Summary: | IMAP crash - pure virtual method called | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Tommi Rantala <tommi.rantala> |
Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | grave | CC: | aalper, djarvie, herbert.fukerider, hrabe, jakob.wilhelm, janne.ojaniemi, jstalnak, kde, mgarski, michael.seiwert, philipp, pmj005, rdm, s.roa, thomas.rusch, thomas, tiggernews, wstephenson, yakuzi2004, zerg2000-bugs.kde.org |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tommi Rantala
2005-11-14 20:49:43 UTC
this looks release critical to me. *** Bug 132060 has been marked as a duplicate of this bug. *** *** Bug 132740 has been marked as a duplicate of this bug. *** Same type of backtrack for kontact 3.5.4 (gentoo) against an IMAP server, and it seems to happen when user is clicking around to different message s rapidly. This crash is the third most common with kontact that we are experiencing (40% are related to bug 126715, 20% to 134701 and about 14% are related to this - overall 20+ crashes per day for 60 users) Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `kontact'. Program terminated with signal 6, Aborted. #0 0xffffe410 in __kernel_vsyscall () Thread 5 (process 9250): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0x49e3b9e6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 No symbol table info available. #2 0x4a745aab in QWaitCondition::wait () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #3 0xb7f1ae85 in KPIM::ThreadWeaver::Weaver::applyForWork () from /usr/kde/3.5/lib/libkdepim.so.1 No symbol table info available. #4 0xb7fb0ae4 in typeinfo name for KPIM::ThreadWeaver::Event () from /usr/kde/3.5/lib/libkdepim.so.1 No symbol table info available. Thread 4 (process 9251): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0x49e3b9e6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 No symbol table info available. #2 0x4a745aab in QWaitCondition::wait () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #3 0xb7f1ae85 in KPIM::ThreadWeaver::Weaver::applyForWork () from /usr/kde/3.5/lib/libkdepim.so.1 No symbol table info available. #4 0x08abdcb0 in ?? () No symbol table info available. Thread 3 (process 9252): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0x49e3b9e6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 No symbol table info available. #2 0x4a745aab in QWaitCondition::wait () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #3 0xb7f1ae85 in KPIM::ThreadWeaver::Weaver::applyForWork () from /usr/kde/3.5/lib/libkdepim.so.1 No symbol table info available. #4 0x08abdcb0 in ?? () No symbol table info available. Thread 2 (process 9253): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0x49e3b9e6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 No symbol table info available. #2 0x4a745aab in QWaitCondition::wait () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #3 0xb7f1ae85 in KPIM::ThreadWeaver::Weaver::applyForWork () from /usr/kde/3.5/lib/libkdepim.so.1 No symbol table info available. #4 0x08abdcb0 in ?? () No symbol table info available. Thread 1 (process 9248): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0x49c2cd3d in raise () from /lib/tls/libc.so.6 No symbol table info available. #2 0x49c2e353 in abort () from /lib/tls/libc.so.6 No symbol table info available. #3 0x4a052dd6 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6 No symbol table info available. #4 0x4a050b8d in __cxxabiv1::__terminate () from /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6 No symbol table info available. #5 0x4a050bc2 in std::terminate () from /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6 No symbol table info available. #6 0x4a05104d in __cxa_pure_virtual () from /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6 No symbol table info available. #7 0xb653d827 in KMReaderWin::setMsg (this=0x88659d8, aMsg=0x8b0dfa8, force=false) at kmreaderwin.cpp:1169 complete = true #8 0xb668ce00 in KMMainWidget::slotMsgSelected (this=0x8914ea0, msg=0x8b0dfa8) at kmmainwidget.cpp:1895 No locals. #9 0xb669dfe3 in KMMainWidget::qt_invoke (this=0x8914ea0, _id=54, _o=0xbffdc4b0) at qucom_p.h:316 No locals. #10 0x4a4a218a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #11 0xb64e8230 in KMHeaders::selected (this=0xbffdc4d8, t0=0x0) at kmheaders.moc:250 clist = (QConnectionList *) 0x88656a0 o = {{type = 0x806a55c, payload = {b = false, c = 0 '\0', s = 0, i = 0, l = 0, uc = 0 '\0', us = 0, ui = 0, ul = 0, f = 0, d = 6.2213875145263882e-266, byte = "\000\000\000\000h\fà\b\002\000\000\000\224_~¶", bytearray = { data = 0x0, size = 148900968}, ptr = 0x0, voidstar = {ptr = 0x0, owner = 104}, charstar = {ptr = 0x0, owner = 104}, utf8 = {ptr = 0x0, owner = 104}, local8bit = {ptr = 0x0, owner = 104}, iface = 0x0, idisp = 0x0}}, {type = 0x806a1e8, payload = {b = 168, c = -88 '¨', s = -8280, i = 145809320, l = 145809320, uc = 168 '¨', us = 57256, ui = 145809320, ul = 145809320, f = 1.0645196e-33, d = -7.8933007599083107e-47, byte = "¨ß°\b\026×\\¶¨ß°\bÊ\000\000", bytearray = {data = 0x8b0dfa8 "hÌ~¶ð-p\b\223J\001", size = 3059537686}, ptr = 0x8b0dfa8, voidstar = {ptr = 0x8b0dfa8, owner = 22}, charstar = { ptr = 0x8b0dfa8 "hÌ~¶ð-p\b\223J\001", owner = 22}, utf8 = { ptr = 0x8b0dfa8 "hÌ~¶ð-p\b\223J\001", owner = 22}, local8bit = { ptr = 0x8b0dfa8 "hÌ~¶ð-p\b\223J\001", owner = 22}, iface = 0x8b0dfa8, idisp = 0x8b0dfa8}}} #12 0xb64e83d9 in KMHeaders::highlightMessage (this=0x8917c80, lvi=0x328, markitread=false) at qguardedptr.h:113 msg = (class KMMessage *) 0x0 #13 0xb64e8848 in KMHeaders::highlightMessage (this=0x0, i=0x0) at kmheaders.cpp:2269 No locals. #14 0xb64f6d51 in KMHeaders::qt_invoke (this=0x8917c80, _id=106, _o=0xbffdc640) at qucom_p.h:316 No locals. #15 0x4a4a218a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #16 0x4a7f777f in QListView::currentChanged () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #17 0x4a58eb78 in QListView::setCurrentItem () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #18 0x4a590f8b in QListView::contentsMousePressEventEx () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #19 0x4a591964 in QListView::contentsMousePressEvent () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #20 0xb71be6b7 in KListView::contentsMousePressEvent () from /usr/kde/3.5/lib/libkdeui.so.4 No symbol table info available. #21 0x00000000 in ?? () No symbol table info available. *** Bug 136337 has been marked as a duplicate of this bug. *** *** Bug 135948 has been marked as a duplicate of this bug. *** The bug happens also in KMail for KDE 3.5.5 (packages made for Kubuntu 6.06) Got new qt-packages from SuSE today: qt-32bit-4.1.0-29.7.x86_64.rpm qt-4.1.0-29.7.x86_64.rpm At least for x86_64, the problem seems to be fixed. No more crashes or invisible mail-bodies so far. Same crash occurred after upgrading to 3.5.5 (gentoo). Frequency seems diminished though. *** Bug 138026 has been marked as a duplicate of this bug. *** Still occurs in KDE 3.5.6 (Gentoo). *** Bug 141541 has been marked as a duplicate of this bug. *** *** Bug 141870 has been marked as a duplicate of this bug. *** *** Bug 142574 has been marked as a duplicate of this bug. *** *** Bug 142887 has been marked as a duplicate of this bug. *** *** Bug 144965 has been marked as a duplicate of this bug. *** I'm forced to discontinue use of Kontact/KMail until this crash issue can be resolved. I'm not happy with multiple crashes per days -- Kontact crashed overnight, and now thrice in three hours. Is there any information I can provide that can help speed resolution of the problem? it does not happen if you use cached-imap (at least for me) On Friday 04 May 2007, Robert Penz wrote: [bugs.kde.org quoted mail] Robert, Thanks for your comment. Where is such a setting? I see only three places in KMail prefs that mention IMAP: 1. Where the mail server host is specified (when the wizard runs). 2. The Store IMAP Password setting (on the same view). 3. The Group IMAP setting. I looked through the Kontact settings and don't find anything there, either. Regards. AKA the 'disconnected imap' account type. Create a new account of that type using your existing settings. This uses the same IMAP protocol as online imap but caches all messages locally for offline reading and syncs changes to message state on every mail check. jstalnak: the information we need to fix the bug is the version of KMail you are using, from which distribution, and how to reliably reproduce the bug. I entered a bug, #144965, and it was marked as a duplicate of this one, which is why I posted to it. Let's see how things work now -- I've created a new account using the cached-imap. Thanks for the suggestion and the instructions on how to do it. Guy On Friday 04 May 2007, Will Stephenson wrote: [bugs.kde.org quoted mail] *** Bug 146069 has been marked as a duplicate of this bug. *** I just hit this bug today, I deleted a bunch of messages by pressing shift-delete and suddenly one message wouldn't get deleted. It was red and overlined and when I tried to delete again kmail crashed. Kubuntu 7.10, (normal imap connection to exchange 2003) kmail: WARNING: FolderStorage::getMsg, message has no sernum, index: 696 #11 0xb58d8fa2 in std::terminate () from /usr/lib/libstdc++.so.6 #12 0xb58d9865 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6 #13 0xb7bdf321 in KMReaderWin::setMsg (this=0x829c790, aMsg=0x88d8800, force=false) at /build/buildd/kdepim-3.5.7enterprise20070926/./kmail/kmreaderwin.cpp:1207 #14 0xb7d4a262 in KMMainWidget::slotMsgSelected (this=0x821e180, msg=0x88d8800) at /build/buildd/kdepim-3.5.7enterprise20070926/./kmail/kmmainwidget.cpp:2126 #15 0xb7d5d2f0 in KMMainWidget::qt_invoke (this=0x821e180, _id=55, _o=0xbfe11744) at ./kmmainwidget.moc:515 #16 0xb5f20893 in QObject::activate_signal (this=0x8246660, clist=0x829a460, o=0xbfe11744) at kernel/qobject.cpp:2356 #17 0xb7b82a4e in KMHeaders::selected (this=0x8246660, t0=0x88d8800) at ./kmheaders.moc:258 #18 0xb7b8a593 in KMHeaders::highlightMessage (this=0x8246660, lvi=0x87f9f70, markitread=false) at /build/buildd/kdepim-3.5.7enterprise20070926/./kmail/kmheaders.cpp:2088 #19 0xb7b8a97c in KMHeaders::highlightMessage (this=0x8246660, i=0x87f9f70) at /build/buildd/kdepim-3.5.7enterprise20070926/./kmail/kmheaders.cpp:2364 #20 0xb7b93306 in KMHeaders::qt_invoke (this=0x8246660, _id=107, _o=0xbfe11888) at ./kmheaders.moc:303 I tried to valgrind kmail but I didn't manage to reproduce the crash. ==30094== Syscall param write(buf) points to uninitialised byte(s) ==30094== at 0x40007F2: (within /lib/ld-2.6.1.so) ==30094== by 0x67D3534: (within /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x67D386E: _IO_do_write (in /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x67D4055: _IO_file_sync (in /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x67C8B6F: fflush (in /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x4356E90: KMFolderMbox::addMsg(KMMessage*, int*) (kmfoldermbox.cpp:1105) ==30094== by 0x4362235: KMFolderImap::slotGetMessagesData(KIO::Job*, QMemArray<char> const&) (kmfolderimap.cpp:1608) ==30094== by 0x4367B9F: KMFolderImap::qt_invoke(int, QUObject*) (kmfolderimap.moc:344) ==30094== by 0x5E9A892: QObject::activate_signal(QConnectionList*, QUObject*) (qobject.cpp:2356) ==30094== by 0x532A8BC: KIO::TransferJob::data(KIO::Job*, QMemArray<char> const&) (jobclasses.moc:993) ==30094== by 0x532A937: KIO::TransferJob::slotData(QMemArray<char> const&) (job.cpp:933) ==30094== by 0x537F3B8: KIO::TransferJob::qt_invoke(int, QUObject*) (jobclasses.moc:1072) ==30094== by 0x5E9A892: QObject::activate_signal(QConnectionList* ==30094== Invalid read of size 4 ==30094== at 0x4014C09: (within /lib/ld-2.6.1.so) ==30094== by 0x400D319: (within /lib/ld-2.6.1.so) ==30094== by 0x4009826: (within /lib/ld-2.6.1.so) ==30094== by 0x687A4B4: (within /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x687A849: _dl_sym (in /lib/tls/i686/cmov/libc-2.6.1.so) ==30094== by 0x64C5DE7: (within /lib/tls/i686/cmov/libdl-2.6.1.so) ==30094== by 0x400D015: (within /lib/ld-2.6.1.so) ==30094== by 0x64C62BB: (within /lib/tls/i686/cmov/libdl-2.6.1.so) ==30094== by 0x64C5D72: dlsym (in /lib/tls/i686/cmov/libdl-2.6.1.so) ==30094== by 0x5A839E8: sys_dl_sym (ltdl.c:646) ==30094== by 0x5A828D5: lt_dlsym (ltdl.c:2664) ==30094== by 0x5931CAE: KLibWrapPrivate::KLibWrapPrivate(KLibrary*, lt_dlhandle_struct*) (klibloader.cpp:278) ==30094== by 0x59C3731: KLibLoader::library(char const*) (klibloader.cpp:443) ==30094== by 0x476B833: KPIM::PluginLoaderBase::openLibrary(QString const&) const (pluginloaderbase.cpp:151) ==30094== by 0x476BB08: KPIM::PluginLoaderBase::mainFunc(QString const&, char const*) const (pluginloaderbase.cpp:124) ==30094== by 0x43F7DCD: KPIM::PluginLoader<KMail::Interface::BodyPartFormatterPlugin, (anonymous namespace)::(anonymous namespace)::BodyPartFormatterPluginLoaderConfig>::createForName(QString const&) const (pluginloader.h:109) ==30094== by 0x43F6D57: KMail::BodyPartFormatterFactory::createFor(char const*, char const*) const (bodypartformatterfactory.cpp:114) ==30094== by 0x43F7D46: KMail::BodyPartFormatterFactory::createFor(QCString const&, QCString const&) const (bodypartformatterfactory.cpp:190) ==30094== by 0x43EC39A: KMail::ObjectTreeParser::parseObjectTree(partNode*) (objecttreeparser.cpp:261) ==30094== by 0x42C330D: KMReaderWin::parseMsg(KMMessage*) (kmreaderwin.cpp:1586) ==30094== by 0x42C3B02: KMReaderWin::displayMessage() (kmreaderwin.cpp:1512) ==30094== by 0x42C3D24: KMReaderWin::updateReaderWin() (kmreaderwin.cpp:1448) ==30094== by 0x42C641B: KMReaderWin::qt_invoke(int, QUObject*) (kmreaderwin.moc:301) ==30094== by 0x5E9A892: QObject::activate_signal(QConnectionList*, QUObject*) (qobject.cpp:2356) *** Bug 159867 has been marked as a duplicate of this bug. *** *** Bug 161315 has been marked as a duplicate of this bug. *** *** Bug 161852 has been marked as a duplicate of this bug. *** *** Bug 185701 has been marked as a duplicate of this bug. *** *** Bug 185700 has been marked as a duplicate of this bug. *** *** Bug 231011 has been marked as a duplicate of this bug. *** *** Bug 162404 has been marked as a duplicate of this bug. *** |