Bug 319766 - Kwin crashes when switching windows with alt-tab
Summary: Kwin crashes when switching windows with alt-tab
Status: RESOLVED DUPLICATE of bug 317765
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.10.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-13 06:19 UTC by Andrea Borgia
Modified: 2013-05-15 13:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Borgia 2013-05-13 06:19:07 UTC
Application: kwin (4.10.2)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.0-20-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:

Unlike other reports which suggest relations with okular or the speed of tab switching, this happens to me quite regularly whenever the system is moderately loaded. Application restarts itself even before the crash dialog appears.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f46853bc7c0 (LWP 2217))]

Thread 3 (Thread 0x7f46690f0700 (LWP 2861)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f46814c9e77 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f46814c9ea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f46787fff8e in start_thread (arg=0x7f46690f0700) at pthread_create.c:311
#4  0x00007f4684bd9e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f4663147700 (LWP 2862)):
#0  0x00007f4684bd2233 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f46800124f3 in qt_safe_select (nfds=13, fdread=0x7f4664000ac8, fdwrite=0x7f4664000d60, fdexcept=0x7f4664000ff8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83
#2  0x00007f4680017499 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f4664000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223
#3  0x00007f4680017c82 in QEventDispatcherUNIX::processEvents (this=0x7f46640008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937
#4  0x00007f467ffe538f in QEventLoop::processEvents (this=this@entry=0x7f4663146d90, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f467ffe5618 in QEventLoop::exec (this=this@entry=0x7f4663146d90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f467fee7410 in QThread::exec (this=this@entry=0x25bc1d0) at thread/qthread.cpp:542
#7  0x00007f467ffc6edf in QInotifyFileSystemWatcherEngine::run (this=0x25bc1d0) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007f467fee9bec in QThreadPrivate::start (arg=0x25bc1d0) at thread/qthread_unix.cpp:338
#9  0x00007f46787fff8e in start_thread (arg=0x7f4663147700) at pthread_create.c:311
#10 0x00007f4684bd9e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f46853bc7c0 (LWP 2217)):
[KCrash Handler]
#6  0x00007f4684ea1c38 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007f4684f0b365 in KWin::Workspace::constrainedStackingOrder (this=this@entry=0x22748c0) at ../../kwin/layers.cpp:558
#8  0x00007f4684f0ba2b in updateStackingOrder (propagate_new_clients=true, this=0x22748c0) at ../../kwin/layers.cpp:119
#9  KWin::Workspace::updateStackingOrder (this=0x22748c0, propagate_new_clients=<optimized out>) at ../../kwin/layers.cpp:112
#10 0x00007f4684f0bbc0 in blockStackingUpdates (this=0x22748c0, block=<optimized out>) at ../../kwin/layers.cpp:665
#11 KWin::Workspace::blockStackingUpdates (this=this@entry=0x22748c0, block=block@entry=false) at ../../kwin/layers.cpp:657
#12 0x00007f4684effa0b in ~StackingUpdatesBlocker (this=<synthetic pointer>, __in_chrg=<optimized out>) at ../../kwin/workspace.h:877
#13 KWin::Client::releaseWindow (this=this@entry=0x2b96890, on_shutdown=on_shutdown@entry=false) at ../../kwin/client.cpp:318
#14 0x00007f4684f18745 in KWin::Client::unmapNotifyEvent (this=this@entry=0x2b96890, e=e@entry=0x7fff4e6b0240) at ../../kwin/events.cpp:730
#15 0x00007f4684f1a84b in KWin::Client::windowEvent (this=0x2b96890, e=e@entry=0x7fff4e6b0240) at ../../kwin/events.cpp:586
#16 0x00007f4684f1bab1 in KWin::Workspace::workspaceEvent (this=0x22748c0, e=e@entry=0x7fff4e6b0240) at ../../kwin/events.cpp:297
#17 0x00007f4684f10568 in KWin::Application::x11EventFilter (this=0x7fff4e6b07a0, e=0x7fff4e6b0240) at ../../kwin/main.cpp:362
#18 0x00007f467f3f80cc in qt_x11EventFilter (ev=0x7fff4e6b0240) at kernel/qapplication_x11.cpp:441
#19 qt_x11EventFilter (ev=0x7fff4e6b0240) at kernel/qapplication_x11.cpp:429
#20 0x00007f467f406170 in QApplication::x11ProcessEvent (this=0x7fff4e6b07a0, event=event@entry=0x7fff4e6b0240) at kernel/qapplication_x11.cpp:3458
#21 0x00007f467f432b39 in QEventDispatcherX11::processEvents (this=0x20edad0, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#22 0x00007f467ffe538f in QEventLoop::processEvents (this=this@entry=0x7fff4e6b04b0, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007f467ffe5618 in QEventLoop::exec (this=this@entry=0x7fff4e6b04b0, flags=...) at kernel/qeventloop.cpp:204
#24 0x00007f467ffeacf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#25 0x00007f467f38affc in QApplication::exec () at kernel/qapplication.cpp:3828
#26 0x00007f4684f1002a in kdemain (argc=1, argv=0x7fff4e6b08e8) at ../../kwin/main.cpp:537
#27 0x00007f4684b01ea5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=1, ubp_av=0x7fff4e6b08e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4e6b08d8) at libc-start.c:260
#28 0x0000000000400701 in _start ()

Possible duplicates by query: bug 319272, bug 319206, bug 317765, bug 315872.

Reported using DrKonqi
Comment 1 Martin Flöser 2013-05-13 06:31:03 UTC

*** This bug has been marked as a duplicate of bug 317765 ***
Comment 2 Andrea Borgia 2013-05-13 06:38:56 UTC
After searching the bug db, I specifically added the comment about okular not being involved to avoid this being marked as a duplicate of 317765. Why do you feel it is related?
Comment 3 Martin Flöser 2013-05-13 06:52:20 UTC
>  Why do you feel it is related?
It's the same backtrace
Comment 4 Thomas Lübking 2013-05-13 09:15:58 UTC
Please post/attach the output of "qdbus org.kde.kwin /KWin supportInformation" and also record whether you're usually using compositing or not.
Comment 5 Andrea Borgia 2013-05-14 21:52:29 UTC
Thomas, here is the link to the info you asked: http://paste.kde.org/743954/
(compositing is off, haven't touched the setting in ages)
Comment 6 Thomas Lübking 2013-05-15 13:39:11 UTC
(In reply to comment #5)
> (compositing is off, haven't touched the setting in ages)

Ok, thanks - stresses the pattern.
You'll unlikely be able to trigger this with compositing and eg. the fade effect. (You can do me a favor and try ;-)