| Summary: | WineTest causes kwin to crash | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Francois Gouget <fgouget> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 4.10.5 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kwin-20131206-034147.kcrash.txt
kwin-20131206-041648.kcrash.txt: kwin-20131206-041821.kcrash.txt kwin-20131206-041821.kcrash.txt |
||
|
Description
Francois Gouget
2013-12-05 06:53:11 UTC
sorry crashes in the nvidia blob. There is nothing we can do about that the bug lacks debug symbols, but ftr. see bug #306709 @francois do the backtraces always look the same? can you install debug packages?: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Created attachment 84017 [details]
kwin-20131206-034147.kcrash.txt
Created attachment 84018 [details]
kwin-20131206-041648.kcrash.txt:
Created attachment 84019 [details]
kwin-20131206-041821.kcrash.txt
Created attachment 84020 [details]
kwin-20131206-041821.kcrash.txt
> @francois > do the backtraces always look the same? No, they are quite different. Also they may be a bit random: I run WineTest 4 times per night but only get one to three crash reports. > can you install debug packages?: I did not find a Debian debug package for kwin but I installed kde-runtime-dbg, kdelibs5-dbg and libqt4-dbg. I uploaded the new backtraces. traces of comment #5 and comment #6 match bug #306709 comment #5 has the deepest known trace: #6 0x00007f8df26eedd0 in vtable for QtSharedPointer::ExternalRefCountData () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f8df23a2a61 in QObject::property (this=0x1fdb290, name=0x7f8df563fbea "visibleRect") at kernel/qobject.cpp:3752 #8 0x00007f8df5630402 in KWin::EffectWindow::expandedGeometry() const () from /usr/lib/libkwineffects.so.1abi4 #9 0x00007f8df563bd81 in KWin::AnimationEffect::updateLayerRepaints() () from /usr/lib/libkwineffects.so.1abi4 #10 0x00007f8df563c62a in KWin::AnimationEffect::triggerRepaint() () from /usr/lib/libkwineffects.so.1abi4 #11 0x00007f8df563cf8d in KWin::AnimationEffect::animate(KWin::EffectWindow*, KWin::AnimationEffect::Attribute, unsigned int, int, KWin::FPx2, QEasingCurve, int, KWin::FPx2) () from /usr/lib/libkwineffects.so.1abi4 ---------------- comment #4 ends deeeeeep in the nvidia blob and is similar to the OP, but the kwin part unfortunately still lacks some debug symbols: #6 0x00007f0892e51854 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #7 0x00007f0892f0bee1 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #8 0x00007f0892c7914a in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #9 0x00007f0892bf6fb9 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #10 0x00007f0892ec1d9c in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #11 0x00007f0892ec215b in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #12 0x00007f0892e68e7a in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #13 0x00007f0892e4c838 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #14 0x00007f089b9264f0 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #15 0x00007f089b92696a in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #16 0x00007f0892bb1a55 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #17 0x00007f0892bb32ad in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #18 0x00007f0892bb3390 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.319.72 #19 0x00007f089bc0f9e5 in KWin::GLRenderTarget::enable() () from /usr/lib/libkwinglutils.so.1abi1 #20 0x00007f089bc0fba5 in KWin::GLRenderTarget::pushRenderTarget(KWin::GLRenderTarget*) () from /usr/lib/libkwinglutils.so.1abi1 #21 0x00007f089bc0ff98 in KWin::GLRenderTarget::attachTexture(KWin::GLTexture const&) () from /usr/lib/libkwinglutils.so.1abi1 #22 0x00007f088102e3d8 in ?? () from /usr/lib/kde4/kwin4_effect_builtins.so #23 0x00007f088102f08c in ?? () from /usr/lib/kde4/kwin4_effect_builtins.so #24 0x00007f089fc92e71 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #25 0x00007f089fc726b1 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #26 0x00007f089fc92dc8 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #27 0x00007f089e0b8821 in KWin::Effect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib/libkwineffects.so.1abi4 ------------------- comment #3 is in password getting =) #0 0x00007f5bed1a649d in __fgetpwent_r (stream=0x7fff79f86110, resbuf=0x7fff79f86110, buffer=0x2d23 <Address 0x2d23 out of bounds>, buflen=18446744073709551615, result=0x7f5bed1a6341 <__GI__nss_files_parse_pwent+433>) at fgetpwent_r.c:77 #1 0x0000000000000000 in ?? () That's rather memory corruption. =============================================== a) tried to reproduce this with xrender compositing? b) can you run kwin in valgrind? |