Bug 289682

Summary:	kmix leaks memory over time and uses 100% CPU
Product:	[Applications] kmix	Reporter:	Silviu C. <silviucc>
Component:	general	Assignee:	Christian Esken <esken>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	silviucc
Priority:	NOR
Version:	4
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi

Description Silviu C. 2011-12-23 17:26:07 UTC

Version:           4 (using Devel) 
OS:                Linux

Over the course of a day of using my computer, listening to music with amarok, browsing the web, watching videos, I find that kmix uses a whopping 1GB+ of my RAM. The system monitor says it uses 25% of my CPU. Top says it's 100%, which means this thing uses one of my four cores .

Also, clicking on the kmix systray button does not make it react instanlty, it lags for a while before displaying anything. It's is still unusable.

Fix is to kill it and restart it

Reproducible: Always

Steps to Reproduce:
Use your KDE desktop, you'll see it

Actual Results:  
Silly memory usage. One core pegged at 100%.

Expected Results:  
None of the above ? :)

Using Kubuntu 11.10 and KDE 4.8 beta 2 packages from the kubuntu ppa.

Comment 1 Silviu C. 2011-12-23 21:26:50 UTC

Created attachment 67070 [details]
New crash information added by DrKonqi

kmix (3.9-plus) on KDE Platform 4.7.90 (4.8 Beta2 (4.7.90) using Qt 4.7.4

- What I was doing when the application crashed:

I was just listening to music, and in between watching a cast on twitch.tv (flashplayer use)

This bug may be related to bug 288675

-- Backtrace (Reduced):
#6  0x00007f810df4d7f3 in MDWSlider::update (this=0x265ea60) at ../../kmix/gui/mdwslider.cpp:990
#7  0x00007f810df490eb in ViewDockAreaPopup::refreshVolumeLevels (this=<optimized out>) at ../../kmix/gui/viewdockareapopup.cpp:159
#8  0x00007f810df46111 in ViewBase::qt_metacall (this=0x2645a60, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff15439680) at ./viewbase.moc:90
#9  0x00007f810df48b08 in ViewDockAreaPopup::qt_metacall (this=0x2645a60, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at ./viewdockareapopup.moc:67
[...]
#11 0x00007f810df64a8c in Mixer::qt_metacall (this=0x25bd7e0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff15439760) at ./mixer.moc:82

Comment 2 Silviu C. 2011-12-23 21:31:55 UTC

Created attachment 67071 [details]
New crash information added by DrKonqi

kmix (3.9-plus) on KDE Platform 4.7.90 (4.8 Beta2 (4.7.90) using Qt 4.7.4

- What I was doing when the application crashed:

I seems it crashes as one songs finishes and the next one starts to play in amarok

-- Backtrace (Reduced):
#6  0x00007faf8157db00 in typeinfo for QGesture () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007faf833f47f6 in MDWSlider::update (this=0x23a8290) at ../../kmix/gui/mdwslider.cpp:990
#8  0x00007faf833f00eb in ViewDockAreaPopup::refreshVolumeLevels (this=<optimized out>) at ../../kmix/gui/viewdockareapopup.cpp:159
#9  0x00007faf833ed111 in ViewBase::qt_metacall (this=0x238f150, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff42d41d70) at ./viewbase.moc:90
#10 0x00007faf833efb08 in ViewDockAreaPopup::qt_metacall (this=0x238f150, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at ./viewdockareapopup.moc:67

Comment 3 Silviu C. 2011-12-23 21:37:48 UTC

Here's a way to reproduce this. Start your KDE session and start playing music with amarok. Watch some youtube. 

At some point, kmix will start using over 1GB of RAM. Kill it and restart it. Listen to various tracks in amarok. Kmix will crash on every song change.

Comment 4 Christian Esken 2011-12-30 12:19:05 UTC

SVN commit 1270928 by esken:

Fix infinite loop leading to 100% CPU usage and excessively allocating memory (on reconstruction a newly connected signal would be implicitely emitted ("again"), which leads to reconstruction and newly connecting the signal, and so forth).
Backport to branch 4.8. Please note that I consider this bug as a showstopper for KDE4.8 (this bug will affect most users, leads to 100% CPU usage, and possibly eat up all available memory).
Related: bug 288675

 M  +33 -1     kmixerwidget.cpp  
 M  +5 -0      kmixerwidget.h  
 M  +11 -0     mdwslider.cpp  
 M  +1 -1      mdwslider.h  
 M  +1 -1      mixdevicewidget.h  
 M  +8 -11     viewbase.cpp  
 M  +3 -1      viewbase.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1270928

Comment 5 Christian Esken 2011-12-30 12:42:55 UTC

Please try again with the newest from branch 4.8 (or trunk). I might have just fixed that today.

Comment 6 Christian Esken 2011-12-30 19:22:24 UTC


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