Bug 306995 - Amarok chews up ~50% CPU, kwin crashed
Summary: Amarok chews up ~50% CPU, kwin crashed
Status: RESOLVED DUPLICATE of bug 196350
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-18 19:14 UTC by Jeffrey
Modified: 2012-09-18 19:16 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 Jeffrey 2012-09-18 19:14:15 UTC
Application: kwin (4.8.4 (4.8.4))
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-3-686-pae i686
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
Trying to use Amarok, which has been extremely CPU-intensive for a while now.  This attempt froze it completely and when I tried to close Amarok, KWin crashed

- Unusual behavior I noticed:
Amarok has been high CPU for a while now and I cannot track down the cause.

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

Thread 2 (Thread 0xb0993b70 (LWP 29780)):
#0  0xb7788424 in __kernel_vsyscall ()
#1  0x4657120a in __pthread_cond_wait (cond=0xb6ef9650, mutex=0xb6ef9638) at pthread_cond_wait.c:153
#2  0x464b732d in __pthread_cond_wait (cond=0xb6ef9650, mutex=0xb6ef9638) at forward.c:139
#3  0xb6de619d in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#4  0xb6de61cf in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#5  0x4656cc39 in start_thread (arg=0xb0993b70) at pthread_create.c:304
#6  0x464aa23e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb35d6950 (LWP 29533)):
[KCrash Handler]
#7  QProcess::setProcessState (this=0x91d9ef8, state=state@entry=QProcess::NotRunning) at io/qprocess.cpp:1770
#8  0xb695bd17 in QProcessPrivate::cleanup (this=this@entry=0x91bfde8) at io/qprocess.cpp:799
#9  0xb69604f5 in QProcessPrivate::_q_processDied (this=0x91bfde8) at io/qprocess.cpp:1058
#10 0xb69605c7 in qt_static_metacall (_a=0xbfcca5a8, _id=13, _o=0x9afe5e0, _c=<optimized out>) at .moc/release-shared/moc_qprocess.cpp:92
#11 QProcess::qt_static_metacall (_o=_o@entry=0x9afe5e0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=13, _a=0xbfcca5a8) at .moc/release-shared/moc_qprocess.cpp:69
#12 0xb69e4ce2 in QMetaObject::activate (sender=0x94e5d78, m=0xb6b30458, local_signal_index=0, argv=0xbfcca5a8) at kernel/qobject.cpp:3547
#13 0xb6a358e5 in QSocketNotifier::activated (this=0x94e5d78, _t1=21) at .moc/release-shared/moc_qsocketnotifier.cpp:103
#14 0xb69eb96f in QSocketNotifier::event (this=0x94e5d78, e=0xbfccaa14) at kernel/qsocketnotifier.cpp:317
#15 0xb5eb547c in QApplicationPrivate::notify_helper (this=0x8d19998, receiver=0x94e5d78, e=0xbfccaa14) at kernel/qapplication.cpp:4556
#16 0xb5eb9e7f in QApplication::notify (this=0xbfccaa14, receiver=0x94e5d78, e=0xbfccaa14) at kernel/qapplication.cpp:3938
#17 0x487790a1 in KApplication::notify (this=0xbfccaeec, receiver=0x94e5d78, event=0xbfccaa14) at ../../kdeui/kernel/kapplication.cpp:311
#18 0xb768612f in notify (e=0xbfccaa14, o=0x94e5d78, this=0xbfccaeec) at ../../kwin/main.cpp:368
#19 KWin::Application::notify (this=0xbfccaeec, o=0x94e5d78, e=0xbfccaa14) at ../../kwin/main.cpp:364
#20 0xb69cc55e in QCoreApplication::notifyInternal (this=0xbfccaeec, receiver=0x94e5d78, event=0xbfccaa14) at kernel/qcoreapplication.cpp:915
#21 0xb69ffb24 in sendEvent (event=0xbfccaa14, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QEventDispatcherUNIX::activateSocketNotifiers (this=this@entry=0x8cc9e88) at kernel/qeventdispatcher_unix.cpp:884
#23 0xb6a006bb in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x8d19a78, flags=..., timeout=0xbfccab78) at kernel/qeventdispatcher_unix.cpp:309
#24 0xb6a01173 in QEventDispatcherUNIX::processEvents (this=0x8cc9e88, flags=...) at kernel/qeventdispatcher_unix.cpp:926
#25 0xb5f69233 in QEventDispatcherX11::processEvents (this=0x8cc9e88, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#26 0xb69cb02c in QEventLoop::processEvents (this=this@entry=0xbfccad68, flags=...) at kernel/qeventloop.cpp:149
#27 0xb69cb321 in QEventLoop::exec (this=0xbfccad68, flags=...) at kernel/qeventloop.cpp:204
#28 0xb69d0a9a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#29 0xb5eb32f4 in QApplication::exec () at kernel/qapplication.cpp:3817
#30 0xb7688cec in kdemain (argc=3, argv=0xbfccb004) at ../../kwin/main.cpp:541
#31 0x0804861b in main (argc=3, argv=0xbfccb004) at kwin_dummy.cpp:3

This bug may be a duplicate of or related to bug 196350.

Possible duplicates by query: bug 302922, bug 301516, bug 300955, bug 295920, bug 290711.

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-09-18 19:16:16 UTC
You actually killed kwin (through the kill helper)

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