Bug 306063

Summary: kwin: random crash while writing an email in kmail
Product: [Plasma] kwin Reporter: Marc Schiffbauer <mschiff>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version First Reported In: 4.9.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Marc Schiffbauer 2012-08-31 09:22:42 UTC 
Application: kwin (4.9.00)
KDE Platform Version: 4.9.00 (Compiled from sources)
Qt Version: 4.8.2
Operating System: Linux 3.5.2-gentoo x86_64
Distribution: "NAME=Gentoo"

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

I am not whether this report is useful at all. The BT seems to be good, but I was just typing an email in kmail when kwin crashed

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5118a297c0 (LWP 15840))]

Thread 2 (Thread 0x7f510b815700 (LWP 15846)):
#0  0x00007f512b884dcc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f512cf9b242 in ?? () from /usr/lib64/qt4/libQtScript.so.4
#2  0x00007f512cf9b279 in ?? () from /usr/lib64/qt4/libQtScript.so.4
#3  0x00007f512c7a7734 in ?? () from /usr/lib64/libGL.so.1
#4  0x00007f512b880ec6 in start_thread () from /lib64/libpthread.so.0
#5  0x00007f51301a29bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5118a297c0 (LWP 15840)):
[KCrash Handler]
#6  0x00007f512af378ff in QRegion::unite (this=<optimized out>, r=...) at painting/qregion.cpp:3997
#7  0x00007f512af381b9 in united (r=..., this=<optimized out>) at ../../include/QtGui/../../src/gui/painting/qregion.h:110
#8  QRegion::operator| (this=<optimized out>, r=...) at painting/qregion.cpp:476
#9  0x00007f513051b844 in KWin::Workspace::windowRepaintsPending() const () from /usr/lib64/libkdeinit4_kwin.so
#10 0x00007f513051bf70 in KWin::Workspace::performCompositing() () from /usr/lib64/libkdeinit4_kwin.so
#11 0x00007f512bc2d309 in QObject::event (this=0x173a350, e=<optimized out>) at kernel/qobject.cpp:1157
#12 0x00007f512ada36a4 in notify_helper (e=0x7fff9ec7f620, receiver=0x173a350, this=0x16dc1b0) at kernel/qapplication.cpp:4551
#13 QApplicationPrivate::notify_helper (this=0x16dc1b0, receiver=0x173a350, e=0x7fff9ec7f620) at kernel/qapplication.cpp:4523
#14 0x00007f512ada83c1 in QApplication::notify (this=0x7fff9ec7fa00, receiver=0x173a350, e=0x7fff9ec7f620) at kernel/qapplication.cpp:3933
#15 0x00007f512fc2ce76 in KApplication::notify (this=0x7fff9ec7fa00, receiver=0x173a350, event=0x7fff9ec7f620) at /var/tmp/portage/kde-base/kdelibs-4.9.49.9999/work/kdelibs-4.9.49.9999/kdeui/kernel/kapplication.cpp:311
#16 0x00007f512bc1474c in QCoreApplication::notifyInternal (this=0x7fff9ec7fa00, receiver=0x173a350, event=0x7fff9ec7f620) at kernel/qcoreapplication.cpp:915
#17 0x00007f512bc45302 in sendEvent (event=0x7fff9ec7f620, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QTimerInfoList::activateTimers (this=0x16dcba8) at kernel/qeventdispatcher_unix.cpp:611
#19 0x00007f512bc45db4 in QEventDispatcherUNIX::processEvents (this=0x162fad0, flags=...) at kernel/qeventdispatcher_unix.cpp:930
#20 0x00007f512ae475d6 in QEventDispatcherX11::processEvents (this=0x162fad0, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#21 0x00007f512bc132a2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#22 0x00007f512bc134f7 in QEventLoop::exec (this=0x7fff9ec7f980, flags=...) at kernel/qeventloop.cpp:204
#23 0x00007f512bc182c5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#24 0x00007f51304cc6b3 in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#25 0x00007f51300de60d in __libc_start_main () from /lib64/libc.so.6
#26 0x0000000000400791 in _start ()

Reported using DrKonqi
Comment 1 Martin Flöser 2012-08-31 09:31:42 UTC 
no sorry, debug symbols for KWin are missing, we only see the method it is crashing but not the line of code and the variables.
Comment 2 Thomas Lübking 2012-08-31 09:54:02 UTC 
Looks like memory corruption - there's no  QRegion::operator| invocation from ::windowRepaintsPending()

Might be a dangeling toplevel pointer, might be sth. entirely different

@Marc
- Do you use KWin as a tiling WM?
- If you get this often or even can reproduce it you could run kwin through valgrind.
Comment 3 Marc Schiffbauer 2012-08-31 10:02:49 UTC 
(In reply to comment #2)
> @Marc
> - Do you use KWin as a tiling WM?

No.

> - If you get this often or even can reproduce it you could run kwin through
> valgrind.

Ok, but it happened the first time. But I will watch out, thanks.
Comment 4 Andrew Crouthamel 2018-09-23 02:38:01 UTC 
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!
Comment 5 Andrew Crouthamel 2018-10-27 03:51:33 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

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