Bug 257295 - Kontact crash while switching KMail->Akregator and pressing KMail-specific button during switch
Summary: Kontact crash while switching KMail->Akregator and pressing KMail-specific bu...
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2010-11-19 02:41 UTC by ancow
Modified: 2017-01-07 22:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description ancow 2010-11-19 02:41:03 UTC
Application: kontact (4.4.7)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-23-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

Due to a timing accident I managed to press the "fetch all email" button from the kmail toolbar right before it was replaced by the akregator toolbar (akregator was already loaded in the main view). Due to the nature of this bug, I didn't manage to try again.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0xb773c730 (LWP 2622))]

Thread 2 (Thread 0xb24f5b70 (LWP 2895)):
#0  0x00f39416 in __kernel_vsyscall ()
#1  0x00add103 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95
#2  0x00a7165f in _L_lock_9687 () from /lib/libc.so.6
#3  0x00a6fe56 in __libc_free (mem=0xacab250) at malloc.c:3736
#4  0x05b78486 in g_free (mem=0xacab250) at /build/buildd/glib2.0-2.26.0/glib/gmem.c:263
#5  0x05b725e7 in g_main_context_unref (context=0xacab250) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:502
#6  0x061fe22d in QEventDispatcherGlib::~QEventDispatcherGlib (this=0xaa2dda0, __in_chrg=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:392
#7  0x060cc5ba in QThreadPrivate::finish (arg=0x9cfa088) at thread/qthread_unix.cpp:302
#8  0x060cce01 in ~__pthread_cleanup_class (arg=0x9cfa088) at /usr/include/pthread.h:545
#9  QThreadPrivate::start (arg=0x9cfa088) at thread/qthread_unix.cpp:271
#10 0x00b62cc9 in start_thread (arg=0xb24f5b70) at pthread_create.c:304
#11 0x00acf6ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb773c730 (LWP 2622)):
[KCrash Handler]
#7  0x00f39416 in __kernel_vsyscall ()
#8  0x00a29941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x00a2ce42 in abort () at abort.c:92
#10 0x00a61305 in __libc_message (do_abort=2, fmt=0xb392a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#11 0x00a6b501 in malloc_printerr (action=<value optimized out>, str=0x6 <Address 0x6 out of bounds>, ptr=0x9c517b8) at malloc.c:6283
#12 0x00a6cd70 in _int_free (av=<value optimized out>, p=<value optimized out>) at malloc.c:4795
#13 0x00a6fe5d in __libc_free (mem=0x9c517b8) at malloc.c:3738
#14 0x060c6fed in qFree (ptr=0x9c517b8) at global/qmalloc.cpp:60
#15 0x06118180 in QString::free (d=0x9c517b8) at tools/qstring.cpp:1151
#16 0xb2ca5a09 in ~QString (this=0xace7c90, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qstring.h:882
#17 KMMsgBase::~KMMsgBase (this=0xace7c90, __in_chrg=<value optimized out>) at ../../kmail/kmmsgbase.cpp:133
#18 0xb2c47987 in KMMsgInfo::~KMMsgInfo (this=0xace7c90, __in_chrg=<value optimized out>) at ../../kmail/kmmsginfo.cpp:153
#19 0xb2cad31b in KMMsgList::clear (this=0x9962ba8, doDelete=true, syncDict=false) at ../../kmail/kmmsglist.cpp:37
#20 0xb2d1a882 in KMFolderMaildir::reallyDoClose (this=0x9962b58) at ../../kmail/kmfoldermaildir.cpp:192
#21 0xb2c2d99d in FolderStorage::close (this=0x0, aForced=62) at ../../kmail/folderstorage.cpp:110
#22 0xb2bfaf36 in KMFolder::close (this=0x9996620, owner=0xb30e8f1f "kmsearch", force=<value optimized out>) at ../../kmail/kmfolder.cpp:554
#23 0xb2e4542b in KMSearch::slotSearchFolderResult (this=0x99fbe00, folder=0x9996620, serNums=..., pattern=0x9655728, complete=true) at ../../kmail/kmfoldersearch.cpp:306
#24 0xb2e46583 in KMSearch::qt_metacall (this=0x99fbe00, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbff91d0c) at ./kmfoldersearch.moc:86
#25 0x061d48ca in QMetaObject::metacall (object=0x99fbe00, cl=2622, idx=8, argv=0xbff91d0c) at kernel/qmetaobject.cpp:237
#26 0x061e76ad in QMetaObject::activate (sender=0x9962b58, m=0xb31f4be8, local_signal_index=21, argv=0x0) at kernel/qobject.cpp:3280
#27 0xb2c2dfab in FolderStorage::searchResult (this=0x9962b58, _t1=0x9996620, _t2=..., _t3=0x9655728, _t4=true) at ./folderstorage.moc:308
#28 0xb2c2f514 in FolderStorage::slotProcessNextSearchBatch (this=0x9962b58) at ../../kmail/folderstorage.cpp:1192
#29 0xb2c2f684 in FolderStorage::qt_metacall (this=0x9962b58, _c=QMetaObject::InvokeMetaMethod, _id=29, _a=0x9d12010) at ./folderstorage.moc:154
#30 0xb2e3d69a in KMFolderIndex::qt_metacall (this=0x9962b58, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0x9d12010) at ./kmfolderindex.moc:69
#31 0xb2d1a80a in KMFolderMaildir::qt_metacall (this=0x9962b58, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0x9d12010) at ./kmfoldermaildir.moc:67
#32 0x061d48ca in QMetaObject::metacall (object=0x9962b58, cl=2622, idx=33, argv=0x9d12010) at kernel/qmetaobject.cpp:237
#33 0x061dfdf6 in QMetaCallEvent::placeMetaCall (this=0x9c0df78, object=0x9962b58) at kernel/qobject.cpp:534
#34 0x061e16a2 in QObject::event (this=0x9962b58, e=0x6) at kernel/qobject.cpp:1219
#35 0x01a7efdc in QApplicationPrivate::notify_helper (this=0x91dd4a0, receiver=0x9962b58, e=0x9c0df78) at kernel/qapplication.cpp:4396
#36 0x01a8504e in QApplication::notify (this=0xbff926f4, receiver=0x9962b58, e=0x9c0df78) at kernel/qapplication.cpp:3798
#37 0x01113cfa in KApplication::notify (this=0xbff926f4, receiver=0x9962b58, event=0x9c0df78) at ../../kdeui/kernel/kapplication.cpp:310
#38 0x061ceb3b in QCoreApplication::notifyInternal (this=0xbff926f4, receiver=0x9962b58, event=0x9c0df78) at kernel/qcoreapplication.cpp:732
#39 0x061d1d8b in sendEvent (receiver=0x0, event_type=0, data=0x91baeb8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#40 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91baeb8) at kernel/qcoreapplication.cpp:1373
#41 0x061d1f4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#42 0x061fda74 in sendPostedEvents (s=0x91e6380) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#43 postEventSourceDispatch (s=0x91e6380) at kernel/qeventdispatcher_glib.cpp:277
#44 0x05b6f855 in g_main_dispatch (context=0x91e6300) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149
#45 g_main_context_dispatch (context=0x91e6300) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702
#46 0x05b73668 in g_main_context_iterate (context=0x91e6300, block=<value optimized out>, dispatch=1, self=0x91dc858) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780
#47 0x05b73848 in g_main_context_iteration (context=0x91e6300, may_block=1) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2843
#48 0x061fd565 in QEventDispatcherGlib::processEvents (this=0x91bab78, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#49 0x01b40be5 in QGuiEventDispatcherGlib::processEvents (this=0x91bab78, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#50 0x061cd609 in QEventLoop::processEvents (this=0xbff92654, flags=) at kernel/qeventloop.cpp:149
#51 0x061cda8a in QEventLoop::exec (this=0xbff92654, flags=...) at kernel/qeventloop.cpp:201
#52 0x061d200f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#53 0x01a7de07 in QApplication::exec () at kernel/qapplication.cpp:3672
#54 0x0804b132 in main (argc=3, argv=0xbff92914) at ../../../kontact/src/main.cpp:224

Possible duplicates by query: bug 252948, bug 243262, bug 242656, bug 238702, bug 236379.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 19:26:22 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:29:06 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.