Application: kmail (2.0.89) KDE Platform Version: 4.5.80 (4.6 Beta1) Qt Version: 4.7.1 Operating System: Linux 2.6.37-rc3-git6-9-desktop x86_64 Distribution: "openSUSE 11.3 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: At some point Kmail refused to show me the contents of mails, so I decided to close it, open akonadi config and restart akonadi. During the shutting down of Akonadi (which takes about a minute) a kmail crash dialog popped up (to my surprise). Hope the backtrace is helpful... BTW while it is basically working, darn, this thing is still full of peculiarities and tiny insects... Not to fast either. Hope you guys and girls manage to find and fix the issues :D hope this helps a bit with that. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f34ca46b760 (LWP 5376))] Thread 2 (Thread 0x7f34c499d710 (LWP 5388)): #0 0x0000003001e0b39c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f34cd99ea94 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #2 0x0000003001e06a4f in start_thread () from /lib64/libpthread.so.0 #3 0x00000030016d082d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f34ca46b760 (LWP 5376)): [KCrash Handler] #6 QString::operator== (this=0x259, other=@0x7fff40722170) at tools/qstring.cpp:2139 #7 0x00007f34d6173926 in QLabel::setText (this=0xacbfd0, text=...) at widgets/qlabel.cpp:339 #8 0x00007f34d6df8f72 in KMCommand::slotJobFinished() () from /usr/lib64/libkmailprivate.so.4 #9 0x00007f34d6df970c in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #10 0x00007f34d69c8fef in QMetaObject::activate (sender=0x24f20f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff407222c0) at kernel/qobject.cpp:3272 #11 0x00007f34d73fd6e2 in KJob::result (this=<value optimized out>, _t1=0x24f20f0) at /usr/src/debug/kdelibs-4.5.80/build/kdecore/kjob.moc:194 #12 0x00007f34d73fd720 in KJob::emitResult (this=0x24f20f0) at /usr/src/debug/kdelibs-4.5.80/kdecore/jobs/kjob.cpp:312 #13 0x00007f34d38c02fd in Akonadi::Job::qt_metacall (this=0x24f20f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xe433c0) at /usr/src/debug/kdepimlibs-4.5.80/build/akonadi/job.moc:91 #14 0x00007f34d3929f95 in Akonadi::ItemFetchJob::qt_metacall (this=0x24f20f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xe433c0) at /usr/src/debug/kdepimlibs-4.5.80/build/akonadi/itemfetchjob.moc:73 #15 0x00007f34d69c7c6a in QObject::event (this=0x24f20f0, e=<value optimized out>) at kernel/qobject.cpp:1211 #16 0x00007f34d5d70cd4 in QApplicationPrivate::notify_helper (this=0x6549e0, receiver=0x24f20f0, e=0x19e1830) at kernel/qapplication.cpp:4445 #17 0x00007f34d5d791ca in QApplication::notify (this=<value optimized out>, receiver=0x24f20f0, e=0x19e1830) at kernel/qapplication.cpp:4324 #18 0x00007f34d797a976 in KApplication::notify (this=0x7fff40722e10, receiver=0x24f20f0, event=0x19e1830) at /usr/src/debug/kdelibs-4.5.80/kdeui/kernel/kapplication.cpp:311 #19 0x00007f34d69b3e2c in QCoreApplication::notifyInternal (this=0x7fff40722e10, receiver=0x24f20f0, event=0x19e1830) at kernel/qcoreapplication.cpp:732 #20 0x00007f34d69b7625 in sendEvent (receiver=0x0, event_type=0, data=0x60c830) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60c830) at kernel/qcoreapplication.cpp:1373 #22 0x00007f34d69de8f3 in sendPostedEvents (s=0x658300) at kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=0x658300) at kernel/qeventdispatcher_glib.cpp:277 #24 0x0000003004240a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x0000003004241270 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x0000003004241510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f34d69dea8f in QEventDispatcherGlib::processEvents (this=0x6128e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #28 0x00007f34d5e15eae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f34d69b3262 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007f34d69b3475 in QEventLoop::exec (this=0x7fff40722cd0, flags=...) at kernel/qeventloop.cpp:201 #31 0x00007f34d69b78db in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #32 0x000000000040316e in _start () Reported using DrKonqi
Hej Jos, any description how to reproduce this issue? I have a vague idea why it crashes, but I don't know how KMail can get into this state. So a step-by-step description would be really helpfull. Ciao, Tobias
Tobias, KMail sometimes stops loading mail folders. I click one, it shows the loading animation on the folder but nothing happens. I close KMail, open Akonadi's settings and let it restart. Then KMail crashed - I thought I had quit it... I'm afraid it is very rare - just one of the things that sometimes happens, I can't reliably reproduce it myself either. If only because sometimes Akonadi just works for a while ;-) Moreover, openSUSE is moving back to the KDEPIM 4.4 as Will doesn't expect the release to be in time for openSUSE 11.4 - a big meh but I understand it. It does however make it hard for me to test it and frankly, as I use the laptop for work, I don't mind it that much. While on the subject, Akonadi also sometimes shows HUGE (as in 5-600 mb in 1-2 sec) memory spikes. No idea why, how or what - but it OOMS thanks to this sometimes. I obviously have a lot of mail (eg folders with 50.000 mails are not uncommon in my setup). Sorry that I couldn't help more.
KMail has become far more reliable - perhaps not perfect but I haven't had issues in months. Great work, everybody!