Application: kmail (4.9 pre) KDE Platform Version: 4.8.00 (4.8.0) (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.2.6-3.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: Just close application, self compiled with qt 4.8 Other KDE application not presents same behavior. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc21353c840 (LWP 10666))] Thread 2 (Thread 0x7fc208291700 (LWP 10669)): #0 0x000000389bc0bae5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fc217e28dd7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /opt/qt4/lib/libQtWebKit.so.4 #2 0x00007fc217e283ac in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /opt/qt4/lib/libQtWebKit.so.4 #3 0x000000389bc07d90 in start_thread () from /lib64/libpthread.so.0 #4 0x000000389b4ef48d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc21353c840 (LWP 10666)): [KCrash Handler] #6 0x000000389b436285 in raise () from /lib64/libc.so.6 #7 0x000000389b437b9b in abort () from /lib64/libc.so.6 #8 0x00007fc21cc21813 in qt_message_output (msgType=QtFatalMsg, buf=0x4cda9b8 "Fatal Error: Accessed global static 'KernelPrivate *sInstance()' after destruction. Defined at /code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:53") at /code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2252 #9 0x00007fc21cc21986 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7fc21b0036a0 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d", ap=0x7fff5252a6f8) at /code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2298 #10 0x00007fc21cc22116 in qFatal (msg=0x7fc21b0036a0 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d") at /code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2481 #11 0x00007fc21afb608f in operator-> (this=<optimized out>) at /code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:53 #12 MailCommon::Kernel::self () at /code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:69 #13 0x00007fc21afa92e9 in MailCommon::FolderCollection::writeConfig (this=0x2f43220) at /code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:200 #14 0x00007fc21afa9d11 in MailCommon::FolderCollection::~FolderCollection (this=0x2f43220, __in_chrg=<optimized out>) at /code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:81 #15 0x00007fc21afa9da9 in MailCommon::FolderCollection::~FolderCollection (this=0x2f43220, __in_chrg=<optimized out>) at /code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:83 #16 0x00007fc21afaa366 in deref (value=0x2f43220, d=0x2f36ed0) at /opt/qt4/include/QtCore/qsharedpointer_impl.h:342 #17 deref (this=<optimized out>) at /opt/qt4/include/QtCore/qsharedpointer_impl.h:336 #18 ~ExternalRefCount (this=<optimized out>, __in_chrg=<optimized out>) at /opt/qt4/include/QtCore/qsharedpointer_impl.h:401 #19 ~QSharedPointer (this=<optimized out>, __in_chrg=<optimized out>) at /opt/qt4/include/QtCore/qsharedpointer_impl.h:466 #20 QMap<long long, QSharedPointer<MailCommon::FolderCollection> >::freeData (this=<optimized out>, x=0x2ce6030) at /opt/qt4/include/QtCore/qmap.h:651 #21 0x000000389b439d4d in __cxa_finalize () from /lib64/libc.so.6 #22 0x00007fc21af4f646 in __do_global_dtors_aux () from /opt/kde/lib/libmailcommon.so.4 #23 0x00007fff5252ab60 in ?? () #24 0x00007fff5252b2e0 in ?? () #25 0x00007fc21aff7c51 in _fini () from /opt/kde/lib/libmailcommon.so.4 #26 0x00007fff5252b2e0 in ?? () #27 0x000000389b00f79d in _dl_fini () from /lib64/ld-linux-x86-64.so.2 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Reported using DrKonqi
please update your kdepim. We fixed it.
*** Bug 296226 has been marked as a duplicate of this bug. ***
Laurent: fixed in 4.8.1 or 4.8.2 ?
*** Bug 296955 has been marked as a duplicate of this bug. ***
Created attachment 70491 [details] New crash information added by DrKonqi kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Kontact 4.8.2 (KDE 4.8.2, Kubuntu 12.04, 64 bit) has crashed on startup. It seems that the old bug is still existing in KDE 4.8.2. -- Backtrace (Reduced): #6 0x00007fd2be8d9445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007fd2be8dcbab in __GI_abort () at abort.c:91 [...] #11 0x00007fd25b10b0bf in operator-> (this=<optimized out>) at ../../mailcommon/mailkernel.cpp:48 #12 MailCommon::Kernel::self () at ../../mailcommon/mailkernel.cpp:64 #13 0x00007fd25b0fae89 in MailCommon::FolderCollection::writeConfig (this=0x1821b30) at ../../mailcommon/foldercollection.cpp:210
Created attachment 72740 [details] New crash information added by DrKonqi kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2 - What I was doing when the application crashed: It looks like this still happens in 4.8.3. I tried to start Kontact, when it crashed. The BT runs through KMail and the same codepath as the initially reported crash. -- Backtrace (Reduced): #11 0x00007f88ff6d2f71 in operator-> (this=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.8.3-r1/work/kmail-4.8.3/mailcommon/mailkernel.cpp:48 #12 0x00007f88ff6d2fd9 in MailCommon::Kernel::self () at /var/tmp/portage/kde-base/kmail-4.8.3-r1/work/kmail-4.8.3/mailcommon/mailkernel.cpp:64 #13 0x00007f88ff6c1780 in MailCommon::FolderCollection::writeConfig (this=0xd82390) at /var/tmp/portage/kde-base/kmail-4.8.3-r1/work/kmail-4.8.3/mailcommon/foldercollection.cpp:210 #14 0x00007f88ff6c1c21 in MailCommon::FolderCollection::~FolderCollection (this=0xd82390, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.8.3-r1/work/kmail-4.8.3/mailcommon/foldercollection.cpp:83 #15 0x00007f88ff6c1cb9 in MailCommon::FolderCollection::~FolderCollection (this=0xd82390, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.8.3-r1/work/kmail-4.8.3/mailcommon/foldercollection.cpp:85
Created attachment 73629 [details] New crash information added by DrKonqi kontact (4.8.5) on KDE Platform 4.8.5 (4.8.5) "release 521" using Qt 4.8.2 - What I was doing when the application crashed: After putting the computer on hibernate state, with kontact closed before the hibernation. I restart the computer. once kde start I get this crash. drkonqi said it's a duplicate of, but then it would prove the fix missed some use case. -- Backtrace (Reduced): #6 0x00007f86562c8d95 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f86562ca2ab in __GI_abort () at abort.c:93 [...] #11 0x00007f85f72fa12a in operator-> (this=<optimized out>) at /usr/src/debug/kdepim-4.8.5/mailcommon/mailkernel.cpp:48 #12 MailCommon::Kernel::self () at /usr/src/debug/kdepim-4.8.5/mailcommon/mailkernel.cpp:64 #13 0x00007f85f72e9fe9 in MailCommon::FolderCollection::writeConfig (this=0x13a5a40) at /usr/src/debug/kdepim-4.8.5/mailcommon/foldercollection.cpp:210
Reopening based on several reports post-4.8.2
*** Bug 307329 has been marked as a duplicate of this bug. ***
Created attachment 74906 [details] New crash information added by DrKonqi kontact (4.9.2) on KDE Platform 4.9.2 using Qt 4.8.3 - What I was doing when the application crashed: The computer started and kontact autostarted. It told me that kontact is already running so i told it to exit. When clicking the button, kontact crashed with this backlog. -- Backtrace (Reduced): #6 0x00007f7f48930425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f7f48933b8b in __GI_abort () at abort.c:91 [...] #11 0x00007f7ee6620587 in operator-> (this=<optimized out>) at ../../mailcommon/mailkernel.cpp:53 #12 MailCommon::Kernel::self () at ../../mailcommon/mailkernel.cpp:69 #13 0x00007f7ee6612c89 in MailCommon::FolderCollection::writeConfig (this=this@entry=0x1e17c40) at ../../mailcommon/foldercollection.cpp:208
Created attachment 76649 [details] New crash information added by DrKonqi kontact (4.10 rc3) on KDE Platform 4.9.98 using Qt 4.8.4 - What I was doing when the application crashed: I tried to start Kontact when it crashed. Did nothing exceptional like having suspended before or so. -- Backtrace (Reduced): #11 0x00007f2f4fd50c0f in operator-> (this=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.9.98/work/kmail-4.9.98/mailcommon/mailkernel.cpp:55 #12 MailCommon::Kernel::self () at /var/tmp/portage/kde-base/kmail-4.9.98/work/kmail-4.9.98/mailcommon/mailkernel.cpp:71 #13 0x00007f2f4fd43969 in MailCommon::FolderCollection::writeConfig (this=0x11e24b0) at /var/tmp/portage/kde-base/kmail-4.9.98/work/kmail-4.9.98/mailcommon/foldercollection.cpp:209 #14 0x00007f2f4fd44491 in MailCommon::FolderCollection::~FolderCollection (this=0x11e24b0, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.9.98/work/kmail-4.9.98/mailcommon/foldercollection.cpp:84 #15 0x00007f2f4fd44529 in MailCommon::FolderCollection::~FolderCollection (this=0x11e24b0, __in_chrg=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.9.98/work/kmail-4.9.98/mailcommon/foldercollection.cpp:86
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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
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.