Bug 256196

Summary:	kwin crashes when KDE the reverse path for other bug
Product:	[Plasma] kwin	Reporter:	Santiago <yoprideone>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Santiago 2010-11-05 23:31:38 UTC

Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

When I was doing the reverse path of the bug report as "Bug 256193", appeared just another problem. Had opened the OpenOffice program and had the Firefox open.
The problem appeared about 5 seconds after opening the program Openoffice and firefox while KDE was doing the reverse path "bug 256193.



Reproducible: Didn't try




Application: KWin (kwin), signal: Aborted
[KCrash Handler]
#6 0x00007f5ceabd39e5 in raise () from /lib64/libc.so.6
#7 0x00007f5ceabd4ee6 in abort () from /lib64/libc.so.6
#8 0x00007f5ce62dfcdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#9 0x00007f5ce62ddef6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007f5ce62ddf23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007f5ce62de076 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#12 0x00007f5ce7515563 in QEventLoop::exec (this=0x7ffff0979480, flags=...) at kernel/qeventloop.cpp:214
#13 0x00007f5ce751988b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#14 0x00007f5ceafc84a4 in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#15 0x00007f5ceabbfb7d in __libc_start_main () from /lib64/libc.so.6
#16 0x0000000000400699 in _start ()

Comment 1 Thomas Lübking 2010-11-06 15:47:57 UTC

crashes right from the core eventloop - unless there's a major bug in QCoreAplication...

...there's either some stackoverflow (the _stupid_ try/catch in QEventLoop shadows such...) but it is rather likely that you ran out of memory (or your RAM is broken) - sorry :-(

-> maybe there's some leak?
if you can reproduce the other bug you should run "top" and watch if some process grows very fast.

For the moment, there's nothing in this report that could be fixed from KDEs side.

Comment 2 Thomas Lübking 2010-12-07 19:13:18 UTC


*** This bug has been marked as a duplicate of bug 241163 ***