Bug 334640

Created attachment 86662 [details]
New crash information added by DrKonqi

krunner (4.11.9) on KDE Platform 4.12.5 using Qt 4.8.6

I have this crash every day after first start and login.

-- Backtrace (Reduced):
#8  0xb6251f7f in pthreadLock::unlock() () from /lib/libkdecore.so.5
#9  0xb6251659 in KSharedDataCache::find(QString const&, QByteArray*) const () from /lib/libkdecore.so.5
#10 0xb6ff252b in KIconLoaderPrivate::findCachedPixmapWithPath(QString const&, QPixmap&, QString&) () from /lib/libkdeui.so.5
#11 0xb6ff2920 in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from /lib/libkdeui.so.5
#12 0xb6fe9c30 in KIconEngine::pixmap(QSize const&, QIcon::Mode, QIcon::State) () from /lib/libkdeui.so.5

*** Bug 336156 has been marked as a duplicate of this bug. ***

*** Bug 334846 has been marked as a duplicate of this bug. ***

*** Bug 334687 has been marked as a duplicate of this bug. ***

Created attachment 87358 [details]
New crash information added by DrKonqi

plasma-desktop (4.11.9) on KDE Platform 4.12.5 using Qt 4.8.6

- What I was doing when the application crashed:

After login, when the splash screen disappears, plasma-desktop crashes with segmentation fault.

-- Backtrace (Reduced):
#8  0x43b1afdf in pthreadLock::unlock() () from /lib/libkdecore.so.5
#9  0x43b1599d in KSharedDataCache::insert(QString const&, QByteArray const&) () from /lib/libkdecore.so.5
#10 0x448d7513 in KIconLoaderPrivate::insertCachedPixmapWithPath(QString const&, QPixmap const&, QString const&) () from /lib/libkdeui.so.5
#11 0x448d80ff in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from /lib/libkdeui.so.5
#12 0x44a9242f in KWindowSystem::icon(unsigned long, int, int, bool, int) () from /lib/libkdeui.so.5

Created attachment 88484 [details]
Crash reporter log

Happened while KDE startup, did nothing special. Fedora 20 x64, kdelibs-4.13.3-1.fc20.x86_64

Created attachment 89822 [details]
New crash information added by DrKonqi

krunner (4.11.12) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

After logging in, I waited for the desktop to be started. Nothing but krunner crashed.

-- Backtrace (Reduced):
#6  0x00007fa90a773838 in _xend () at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  __lll_unlock_elision (lock=0x7fa8fd6e0008, private=128) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x00007fa912686b06 in unlock (this=0x2641d30) at ../../kdecore/util/kshareddatacache.cpp:1245
#9  ~CacheLocker (this=<synthetic pointer>, __in_chrg=<optimized out>) at ../../kdecore/util/kshareddatacache.cpp:1317
#10 KSharedDataCache::insert (this=0x2643110, key=..., data=...) at ../../kdecore/util/kshareddatacache.cpp:1595

I also get this extremely often with KDELibs 4.14.8, for me it's the kwallet service that's crashing.

Application: KDE Wallet Service (kwalletd), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f07c7650080 in __lll_unlock_elision () from /usr/lib/libpthread.so.0
#7  0x00007f07c6cfc5d2 in KSharedDataCache::find(QString const&, QByteArray*) const () from /usr/lib/libkdecore.so.5
#8  0x00007f07c71a6476 in ?? () from /usr/lib/libkdeui.so.5
#9  0x00007f07c71a683c in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from /usr/lib/libkdeui.so.5
#10 0x00007f07c719d9ef in ?? () from /usr/lib/libkdeui.so.5
#11 0x00007f07c58ca535 in QIcon::pixmap(QSize const&, QIcon::Mode, QIcon::State) const () from /usr/lib/libQtGui.so.4
#12 0x00007f07c58bbdaf in QWidgetPrivate::setWindowIcon_sys(bool) () from /usr/lib/libQtGui.so.4
#13 0x00007f07c586f573 in QWidget::setWindowIcon(QIcon const&) () from /usr/lib/libQtGui.so.4
#14 0x00007f07c7172801 in KPasswordDialog::KPasswordDialog(QWidget*, QFlags<KPasswordDialog::KPasswordDialogFlag> const&, QFlags<KDialog::ButtonCode>) () from /usr/lib/libkdeui.so.5
#15 0x00007f07c8093dfa in ?? () from /usr/lib/libkdeinit4_kwalletd.so
#16 0x00007f07c8095f63 in ?? () from /usr/lib/libkdeinit4_kwalletd.so
#17 0x00007f07c80977e6 in ?? () from /usr/lib/libkdeinit4_kwalletd.so
#18 0x00007f07c80983d8 in ?? () from /usr/lib/libkdeinit4_kwalletd.so
#19 0x00007f07c64ef071 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00007f07c58249fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#21 0x00007f07c582b458 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#22 0x00007f07c71f483a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#23 0x00007f07c64d5e4d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#24 0x00007f07c64d9211 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#25 0x00007f07c6504e13 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00007f07c1ea99fd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f07c1ea9ce0 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f07c1ea9d8c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f07c6504f5d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007f07c58c8326 in ?? () from /usr/lib/libQtGui.so.4
#31 0x00007f07c64d49a1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0x00007f07c64d4d05 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x00007f07c64da2a9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#34 0x00007f07c8089803 in kdemain () from /usr/lib/libkdeinit4_kwalletd.so
#35 0x00007f07c7cf6790 in __libc_start_main () from /usr/lib/libc.so.6
#36 0x0000000000400719 in _start ()

I just found https://bbs.archlinux.org/viewtopic.php?id=197100 pointing to https://www.archlinux.org/news/changes-to-intel-microcodeupdates/ . Indeed, I was missing that on my arch box here and adding the opcode updater fixed the issue for me.

@everyone else: can you make sure to update your microcodes and check whether the problem still occurs?

I just made sure my machine had the newest Intel microcodes installed (by following http://askubuntu.com/questions/545925/how-to-update-intel-microcode-properly).

Judging by the fact that the crash has not occured for a rather long time now, this issue seems to be solved on my machine.

The microcode update just hides the problem. I suppose it disabled the TSX feature for your CPU. As far as I know there have been some bugs in the early implementations. On my new Skylake Xeon TSX is available and for me on almost every login a Bunch of KDE application crashes. They run properly after restarting them manually.
I have looked a little bit into the KShareDataCache code. It looks to me that there are a lot of places for exceptions or error returns which might leave the mutex in some locked or unlocked state when it is recreated afterwards. TSX seems to be very sensitive against wrong usage of mutexes.
For tests I have disabled TSX mutexes by setting the mutex type to "Error Checking Mutex". I did not observe any crashes since then. Here is the change I made:
--- a/kdecore/util/kshareddatacache_p.h
+++ b/kdecore/util/kshareddatacache_p.h
@@ -199,6 +199,9 @@
         // Initialize attributes, enable process-shared primitives, and setup
         // the mutex.
         if (::sysconf(_SC_THREAD_PROCESS_SHARED) >= 200112L && pthread_mutexattr_init(&mutexAttr) == 0) {
+            // Use error check mutex to disable TSX mutex
+            pthread_mutexattr_settype(&mutexAttr, PTHREAD_MUTEX_ERRORCHECK);
+
             if (pthread_mutexattr_setpshared(&mutexAttr, PTHREAD_PROCESS_SHARED) == 0 &&
                 pthread_mutex_init(&m_mutex, &mutexAttr) == 0)
             {

Created attachment 97848 [details]
Backtrace of crash

Here is a backtrace of a crash

*** Bug 365358 has been marked as a duplicate of this bug. ***

*** Bug 369373 has been marked as a duplicate of this bug. ***

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

(In reply to Andrew Crouthamel from comment #15)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least 15 days.
> Please provide the requested information as soon as possible and set the bug
> status as REPORTED. Due to regular bug tracker maintenance, if the bug is
> still in NEEDSINFO status with no change in 30 days, the bug will be closed
> as RESOLVED > WORKSFORME due to lack of needed information.
 
Hi,

it's been 4 years ago since I have reported this bug. I think you can close it.