Bug 10702

Summary:	Kmix is using tons of RAM
Product:	Mageia	Reporter:	M D <crxssi>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, lmenut, mageia, mageia
Version:	3
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	kmix-4.10.2-1.mga3	CVE:
Status comment:
Bug Depends on:	10600
Bug Blocks:

Description M D 2013-07-05 01:50:24 CEST

This is the second time I have noticed that kmix is using a totally unreasonable amount of memory and it is so significant I am reporting it as a bug:

$ top
kmix  VIRT: 1298m  RES=625m  SHR=9948  TIME+=19:22.47

$ uptime
 19:41:53 up 12 days,  8:37,  6 users,  load average: 0.10, 0.12, 0.09

If I kill it, and restart it:
kmix  VIRT: 688m  RES=23m  SHR=15m  TIME+=0:00.17

Notice the change in shared memory- it actually goes UP when it is restarted,  and resident memory drops *600MB*!

After running for several minutes, it is already using more memory:
kmix  VIRT: 692m  RES=27m  SHR=15m  TIME+=0:00.48

I have no idea if there is something I am running or doing that causes kmix to start using up memory and not releasing it.  I have a Soundblaster Live! card and no other sound card enabled.  I typically leave Audacious running (and usually idle) and also Pidgin which uses sound occasionally.  My hardware is all identical to when I was running Mageia 2, and I run all the same apps, and I never had this issue in the past.

Reproducible: 

Steps to Reproduce:

Comment 1 Sander Lepik 2013-07-05 10:31:47 CEST

Is it fresh profile or profile from Mageia 2 (or even earlier)?

You could try to delete KMix's conf and see if that helps:

Quit KMix

rm -rf ~/.kde4/share/config/kmix* ~/.kde4/share/apps/kmix/

Restart KMix

CC: (none) => mageia

Comment 2 M D 2013-07-05 14:57:57 CEST

This morning, several hours later, it has used more memory again:

kmix  VIRT: 719m  RES=54m  SHR=15m  TIME+=0:05.90

I am wiping any stored config by removing (actually renaming) these and restarting:

$HOME/.kde4/share/config/kmixctrlrc
$HOME/.kde4/share/config/kmixrc

kmix  VIRT: 688m  RES=25m  SHR=17m  TIME+=0:00.18

Will keep an eye on it and see what happens.

Comment 3 M D 2013-07-06 03:55:59 CEST

Nope, clearing the settings made no difference.  Kmix just keeps eating more and more memory.  Now it is:

kmix  VIRT: 776m  RES=111m  SHR=17m  TIME+=0:26.76

That is double the RAM in just a half a day.  And I haven't "opened" the application or used it to adjust the volume at all.

Comment 4 Sander Lepik 2013-07-06 13:03:54 CEST

Anything interesting in ~/.xsession-errors ?

Comment 5 M D 2013-07-06 14:01:28 CEST

>"Anything interesting in ~/.xsession-errors ?"

When I relaunch it, I get these:

sConnection for control created "/Mixers/PulseAudio__Playback_Devices_1/alsa_output_pci_0000_01_06_0_analog_stereo" 
QDBusConnection for control created "/Mixers/PulseAudio__Capture_Devices_1/alsa_input_pci_0000_01_06_0_analog_stereo" 
QDBusConnection for control created "/Mixers/PulseAudio__Playback_Streams_1/stream_3897" 
QDBusConnection for control created "/Mixers/PulseAudio__Playback_Streams_1/restore_sink_input_by_media_role_event" 
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00064
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c0005b
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00052
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00049
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00040
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00037
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c0002e
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2c00025
plasma-desktop(2897)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2897)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 

And the last messages repeat every now and then, seemingly at random times- but is not related to kmix running (does that even without it running).  I have 751 of those in the file. 

When quitting kmix, I get these:

kded(2852)/kmix sink_input_cb: Ignoring sink-input due to it being designated as an event and thus handled by the Event slider 
kmix(19214) sink_input_cb: Ignoring sink-input due to it being designated as an event and thus handled by the Event slider

Comment 6 Sander Lepik 2013-07-06 14:38:06 CEST

Seems to be upstream bug: https://bugs.kde.org/show_bug.cgi?id=309464

Not sure if the last commit in the bug will fix it or not, at least it's not marked as fixed yet..

CC: (none) => balcaen.john, lmenut, nicolas.lecureuil
Hardware: x86_64 => All

Comment 7 John Balcaen 2013-07-07 00:24:11 CEST

Patch added on kmix package for the 4.10.5 update.

Blocks: (none) => 10600

Comment 8 M D 2013-07-07 06:08:50 CEST

(In reply to John Balcaen from comment #7)
> Patch added on kmix package for the 4.10.5 update.

(In reply to Sander Lepik from comment #6)
> Seems to be upstream bug: https://bugs.kde.org/show_bug.cgi?id=309464
> 
> Not sure if the last commit in the bug will fix it or not, at least it's not
> marked as fixed yet..

Yep, I was expecting it would be upstream (most things are) but wanted to let the Mageia team know it is happening so it can hopefully be updated/patched to fix.  I will monitor this thread and if/when an update to kmix is pushed out, I will report back it if fixed the issue.

It is amazing just how many memory leaks they have been dealing with... it is just kmix!

Comment 9 Sander Lepik 2013-07-11 12:21:34 CEST

Until 4.10.5 is tested and released, you can use this rpm: https://www.dropbox.com/s/5h2epajtef24owl/kmix-4.10.2-1.1.mga3.x86_64.rpm - at least for me it fixed the memory leak. When before the memory usage reached 150MB+ then now after 3 days it's still @ 29MB (it was the same when freshly started).

John Balcaen 2013-07-11 22:35:30 CEST

Blocks: 10600 => (none)
Depends on: (none) => 10600

Comment 10 M D 2013-09-01 14:56:39 CEST

(In reply to Sander Lepik from comment #9)
> Until 4.10.5 is tested and released, you can use this rpm:
> https://www.dropbox.com/s/5h2epajtef24owl/kmix-4.10.2-1.1.mga3.x86_64.rpm -
> at least for me it fixed the memory leak. When before the memory usage
> reached 150MB+ then now after 3 days it's still @ 29MB (it was the same when
> freshly started).

I have tested that RPM for weeks and it appears to work fine, just like you said.  Thanks.

Comment 11 Manuel Hiebel 2013-09-01 16:06:01 CEST

and it was pushed with the kde update, closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED