| Summary: | KWin crashes after running KAlgebra from git under valgrind and then pressing the Kickoff menu item. | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Shlomi Fish <shlomif> |
| Component: | kshareddatacache | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | christian.gonzalez, mpyne, mwoehlke.floss, rasasi78 |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.12.97 | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=333475 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Shlomi Fish
2014-04-17 17:46:43 UTC
Created attachment 87902 [details] New crash information added by DrKonqi kwin (4.11.10) on KDE Platform 4.12.5 using Qt 4.8.6 Similar crash, same circumstances... running an application under valgrind takes down kwin. For me this is 100% reproducible with a development build of Slicer (http://www.slicer.org/), although that's a bit excessive as a test case, but valgrind, and not the specific application running in valgrind, appears to be the critical component. -- Backtrace (Reduced): #6 0x0000003866e11314 in _xbegin () at ../nptl/sysdeps/unix/sysv/linux/x86/hle.h:53 #7 __lll_timedlock_elision (futex=futex@entry=0x7f1b9fc4c008, adapt_count=adapt_count@entry=0x7f1b9fc4c01c, t=0x7fff6d02dd40, private=128) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-lock.c:56 #8 0x0000003866e0ab17 in pthread_mutex_timedlock (mutex=0x7f1b9fc4c008, abstime=0x7fff6d02dd40) at ../nptl/pthread_mutex_timedlock.c:103 #9 0x000000318d83ca5c in pthreadTimedLock::lock (this=0xbaf9e0) at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache_p.h:252 #10 0x000000318d83b93a in lock (this=0xba4a70) at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1236 FWIW I can confirm that the same thing happens with 'valgrind /usr/bin/kcalc'. This is what I got: kde-svn@midna ~ $ valgrind $(which kcalc) ==3063== Memcheck, a memory error detector ==3063== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==3063== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==3063== Command: /home/kde-svn/kde-4/bin/kcalc ==3063== ==3063== Conditional jump or move depends on uninitialised value(s) ==3063== at 0x4018154: index (in /lib64/ld-2.19.so) ==3063== by 0x400755D: expand_dynamic_string_token (in /lib64/ld-2.19.so) ==3063== by 0x40076EC: fillin_rpath (in /lib64/ld-2.19.so) ==3063== by 0x4007E96: _dl_init_paths (in /lib64/ld-2.19.so) ==3063== by 0x4002CCA: dl_main (in /lib64/ld-2.19.so) ==3063== by 0x40157EB: _dl_sysdep_start (in /lib64/ld-2.19.so) ==3063== by 0x4004AEB: _dl_start (in /lib64/ld-2.19.so) ==3063== by 0x40011A7: ??? (in /lib64/ld-2.19.so) ==3063== ==3063== Conditional jump or move depends on uninitialised value(s) ==3063== at 0x4018154: index (in /lib64/ld-2.19.so) ==3063== by 0x400755D: expand_dynamic_string_token (in /lib64/ld-2.19.so) ==3063== by 0x4008187: _dl_map_object (in /lib64/ld-2.19.so) ==3063== by 0x40013DD: map_doit (in /lib64/ld-2.19.so) ==3063== by 0x400EC52: _dl_catch_error (in /lib64/ld-2.19.so) ==3063== by 0x4000B30: do_preload (in /lib64/ld-2.19.so) ==3063== by 0x40041BC: dl_main (in /lib64/ld-2.19.so) ==3063== by 0x40157EB: _dl_sysdep_start (in /lib64/ld-2.19.so) ==3063== by 0x4004AEB: _dl_start (in /lib64/ld-2.19.so) ==3063== by 0x40011A7: ??? (in /lib64/ld-2.19.so) ==3063== ==3063== ==3063== HEAP SUMMARY: ==3063== in use at exit: 335,831 bytes in 4,508 blocks ==3063== total heap usage: 473,709 allocs, 469,201 frees, 102,637,856 bytes allocated ==3063== ==3063== LEAK SUMMARY: ==3063== definitely lost: 3,592 bytes in 31 blocks ==3063== indirectly lost: 9,488 bytes in 83 blocks ==3063== possibly lost: 4,676 bytes in 83 blocks ==3063== still reachable: 318,075 bytes in 4,311 blocks ==3063== suppressed: 0 bytes in 0 blocks ==3063== Rerun with --leak-check=full to see details of leaked memory ==3063== ==3063== For counts of detected and suppressed errors, rerun with: -v ==3063== Use --track-origins=yes to see where uninitialised values come from ==3063== ERROR SUMMARY: 3 errors from 2 contexts (suppressed: 0 from 0) No crashes (but my Kickoff button is for Homerun Applet, so I'll try again with that as well, or see if I can find the bug from the bt itself). Likewise with real Kickoff. It's annoying in that regard being the KSharedDataCache maintainer—it really doesn't *ever* crash for me, only for others! :( *** Bug 341440 has been marked as a duplicate of this bug. *** This issue unfortunately still exists see bug #361426. There, you also can find a backtrace of KAte crashing with a recent version (2016-09-06). *** This bug has been marked as a duplicate of bug 361426 *** |