Huge memory leak in Rhythmbox

[Александар]

Hi...
I'm using Ubuntu 9.04 x64 version ( kernel 2.6.28-15-generic ), and i noticed that my RAM is 50% used (that is too much for my PC with 4 GB of RAM), I checked and i saw that Rhythmbox uses more than 1.4 GB of RAM... So I wanna report this bug and i hope you will fix this.
Thank you.

[Nicola Ferralis (feranick)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in rhythmbox.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[Joe McDonagh (joseph-e-mcdonagh)]

This is reproducible on my machine just by leaving RhythmBox open for a long period of time. One day when it was on for a couple weeks it had something like >100GB VIRT, resident was pretty high most of my RAM was taken by it and tons of swapping was happening. On this machine I have a somewhat large music collection, ~20k audio files, not sure if it has something to do with large libraries.

[Joe McDonagh (joseph-e-mcdonagh)]

I can't be the only person seeing this bug:

28015 jmcdonag 20 0 42.3g 1.2g 16m S 4 32.5 14:28.80 rhythmbox

I just watched it ask for approximately 100 MB per every two seconds... All I have to do is let rhythmbox stay open for a while. Is there some way I can run it in debug mode and give you more information?

[Edwin Wong (wong-edwin)]

Just wanted to confirm that I appear to be seeing the same bug in Ubuntu 9.04, albeit in the 32-bit kernel (2.6.28-15-generic). There seems to be a specific trigger before memory starts leaking on my system. RAM usage is pretty reasonable for a while, from about 25-30MB while doing normal tasks in Rhythmbox, then something happens and it starts using 10 extra MB of RAM every two seconds or so. This is in a relatively small music collection, 270 songs totalling 1.1 GB.

[requeth (requeth-hotmail)]

Just want to bump this bug to make sure it's still being looked at. I'm still having this issue with Ubuntu 9.04. My library is 2.2gb and after leaving Rhythmbox open for 6 hours Rhythmbox is using just shy of 900MB of ram. For those of us with only 2GB of ram this is a serious hog, plus it's cranking my hard drive due to swap and I'm worried about burnout.

[Александар (aceristovski)]

Hmm, I've noticed that when i press "next song" key on my keyboard Rhythmbox is using aditional memory...
It's the same with automatic shifting the song, Rhythmbox use extra memory for that!
But, probably that is not the problem because leak is too big.
I'm using Karmic now, and there is no memory leak in Rhythmbox, except "shifting song" problem, that was(is) present in Jaunty too.

[Shaun Thomas (shaun-bonesmoses)]

I'll pipe in here. I just killed rhythmbox because:

ps axo rss,command:50,pid | sort -nr | head -1

366280 rhythmbox 2452

Really? After restarting it, it's at about 30MB. I can't imagine why playing a list of OGG files is so demanding, but apparently it is. I'll just have to switch to mpd until this is resolved.

[Daniel (daniel-matthis)]

Looked through and could not find any other one that addressed this but I'm now having this issue in Lucid (yes i know, it's beta)

I ran rhythmbox on 9.10 with no issue unless I left it open for days (5 to 10) in which case I would see it clime to 500 MB maybe 600. Now I can max out the available memory in maybe an hour. This is on the same system. I just did an in place install.

If I close rhythmbox then the memory is released and I can start it up again, but in an hour or two it will max out the memory again.

[Robert Lockhart (immaculate-macbeth)]

I'm getting something like this too. Running lucid, rhythmbox has started to become unresponsive after seconds of it starting. It'll then swallow 100% of CPU and 1.1 GiB of memory, and sit there bloated until I kill it.

Ran without issue on karmic and for the first few days on lucid, so I have no idea what's changed, sorry.

[Paul Gortmaker (paul-gortmaker)]

If you have a crapload of files in your home dir, then rythmbox, in its infinite wisdom will try and index your complete home dir, and also try to setup an inotify against every file it finds, which from memory (and strace) will eventually cause it to get reams and reams of ENOSPC returns, which it ignores and bravely continues on requesting more inotify. (yes, that is a bug).

To change the defaults from this insane behaviour, kill it (if you haven't already) and restart. Immediately after restarting, go into

Edit -> Preferences -> Music

and untick the "Watch my library for new files"

and then exit again, to ensure any indexing it spawned off won't be left running to completion

Then optionally once you restart, go back to the same menu, and where it has "Music files are placed in", go and enter a single sane dir where you want it to index. i.e. /home/mymusic or whatever.

There isn't a way in the gui to see where it will go index, so check the XML file in $HOME/.gconf/apps/rhythmbox/ and check %gconf.xml for library_locations to make sure it doesn't have a bunch of junk paths.

Finally, if you are brave, you can try experimenting with re-enabling the "Watch for new files" - and see if it sticks to the path you gave it above.

[Jason Spashett (jspashett)]

Yes the same bug is present in 10.04 and it uses a huge amount of memory over time, days for example. I ran valgrind on the binary (not in debug) and it says:

==5405== HEAP SUMMARY:
==5405== in use at exit: 26,125,414 bytes in 119,426 blocks
==5405== total heap usage: 707,791 allocs, 588,365 frees, 136,164,359 bytes allocated
==5405==
==5405== LEAK SUMMARY:
==5405== definitely lost: 11,416 bytes in 34 blocks
==5405== indirectly lost: 30,496 bytes in 949 blocks
==5405== possibly lost: 13,211,012 bytes in 91,511 blocks
==5405== still reachable: 12,872,490 bytes in 26,932 blocks
==5405== suppressed: 0 bytes in 0 blocks
==5405== Rerun with --leak-check=full to see details of leaked memory

[Omer Akram (om26er)]

if you are still facing this issue then please provide the Valgrind logs by following the instruction here https://wiki.ubuntu.com/Valgrind so that we could send this bug report to the people writing rhythmbox.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]