Bug 315300

Summary:	Kwin crashes when Firefox opened 2 Facebook-pages
Product:	[Plasma] kwin	Reporter:	Kocsis András <drisank>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	Keywords:	triaged
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kocsis András 2013-02-17 00:10:47 UTC

Application: kwin (4.8.5 (4.8.5) "release 2")
KDE Platform Version: 4.8.5 (4.8.5) "release 2"
Qt Version: 4.8.1
Operating System: Linux 3.4.28-2.20-default i686
Distribution: "openSUSE 12.2 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
In Firefox 18.0 I used Facebook, where I opened a FB-link on a new page (with the same account, certainly). After that I got a crash report "Kwin crashes", and I couldn't do anything in Firefox, I had to kill that with Ctrl-Alt-Esc, and restart. (After kill the Firefox the problem is finished.)

- Unusual behavior I noticed:
After crash the Firefox-window minimize and maximize again and again, and it opened new KBugs-windows with the same crash report until I kill the Firefox.

The crash can be reproduced some of the time.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1c61740 (LWP 8197))]

Thread 2 (Thread 0xa5e9eb40 (LWP 8223)):
#0  0xb7760430 in __kernel_vsyscall ()
#1  0xb5d9fa4c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb754411c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb66201fd in ?? () from /usr/lib/libQtScript.so.4
#4  0xb662022f in ?? () from /usr/lib/libQtScript.so.4
#5  0xb5d9be32 in start_thread () from /lib/libpthread.so.0
#6  0xb75367ee in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb1c61740 (LWP 8197)):
[KCrash Handler]
#6  0xb7760430 in __kernel_vsyscall ()
#7  0xb747a31f in raise () from /lib/libc.so.6
#8  0xb747bc03 in abort () from /lib/libc.so.6
#9  0xb521801d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#10 0xb5215c93 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb5215ccf in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0xb5215fc5 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb5f2cfb7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#14 0xb5f31cea in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#15 0xb53fe934 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#16 0xb7645bec in kdemain () from /usr/lib/libkdeinit4_kwin.so
#17 0x080485bb in ?? ()
#18 0xb74653d5 in __libc_start_main () from /lib/libc.so.6
#19 0x080485e1 in _start ()

Possible duplicates by query: bug 315254, bug 315125, bug 315042, bug 315017, bug 314753.

Reported using DrKonqi

Comment 1 Thomas Lübking 2013-02-17 00:50:37 UTC

:-(
Not again.

To debug this and in case you can reproduce the issue (seems) please gdb attach to kwin from VT1, continue and then cause the crash.

There's unfortunately no other way (see bug #268384 and bug #241163 - this is -likely- an exception from "new" memory allocation which raises an abort in the Qt event chain)

Do you need assistance on this (VT1, gdb, gdb logging)?

Comment 2 Christoph Feck 2013-02-24 14:08:41 UTC

If you can provide the information requested in comment #1, please add it.

For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash

Comment 3 Martin Flöser 2013-04-05 13:33:44 UTC

see comment #2.

Comment 4 Andrew Crouthamel 2018-09-24 02:18:36 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 02:53:37 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!