Version: unspecified (using Devel) OS: Linux On quitting KAlarm, I got the following crash in Akonadi plugin cleanup routines, in KCleanUpGlobalStatic. It could possibly be a problem with KCleanUpGlobalStatic - see bug 257646 for another KCleanUpGlobalStatic crash (in Oxygen). Application: KAlarm (kalarm), signal: Segmentation fault [KCrash Handler] #6 0xb528a6b6 in QHashData::free_helper () from /opt/qt4.7/lib/libQtCore.so.4 #7 0xb7366809 in QHash<QByteArray, Akonadi::PluginEntry>::freeData (this=0x9d59270, x=0x9d30220) at /opt/qt4.7/include/QtCore/qhash.h:568 #8 0xb7366931 in ~QHash (this=0x9d59270) at /opt/qt4.7/include/QtCore/qhash.h:284 #9 0xb7369c44 in ~MimeTypeEntry (this=0x9d5926c) at /home/david/src/svn/trunk/KDE/kdepimlibs/akonadi/typepluginloader.cpp:126 #10 0xb7369cc6 in std::_Destroy<Akonadi::MimeTypeEntry> (__pointer=0x9d5926c) at /usr/include/c++/4.3/bits/stl_construct.h:88 #11 0xb7369ce7 in std::_Destroy<Akonadi::MimeTypeEntry*> (__first=0x9d5926c, __last=0x9d592a8) at /usr/include/c++/4.3/bits/stl_construct.h:103 #12 0xb7369f43 in std::_Destroy<Akonadi::MimeTypeEntry*, Akonadi::MimeTypeEntry> (__first=0x9d591e8, __last=0x9d592a8) at /usr/include/c++/4.3/bits/stl_construct.h:128 #13 0xb736a0a8 in ~vector (this=0x9d2c7c8) at /usr/include/c++/4.3/bits/stl_vector.h:300 #14 0xb736aaad in ~PluginRegistry (this=0x9d2c7c8) at /home/david/src/svn/trunk/KDE/kdepimlibs/akonadi/typepluginloader.cpp:226 #15 0xb735f8b9 in destroy () at /home/david/src/svn/trunk/KDE/kdepimlibs/akonadi/typepluginloader.cpp:383 #16 0xb7218aef in ~KCleanUpGlobalStatic (this=0xb742bce8) at /opt/kde4/include/kglobal.h:62 #17 0xb4f92ab9 in exit () from /lib/i686/cmov/libc.so.6 #18 0xb4f7a45d in __libc_start_main () from /lib/i686/cmov/libc.so.6 #19 0x080822b1 in _start () Reproducible: Didn't try
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 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.