GNOME Bugzilla – Bug 677738
Rhythmbox leaking large amounts of memory
Last modified: 2018-05-24 17:29:59 UTC
Hola, I decided to forward this bug from Launchpad: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/976534 in order to get more attention from the devs. Maybe someone on Launchpad is willing to help with debugging or so. In that case you have to ask them. There's a very big and ugly memory leak somewhere in Rhythmbox in Ubuntu 12.04 in both 2.96 and 2.97 that I grabbed from webupd8.org ppa. In my case, just after five or so minutes of playing Rhythmbox memory consumption reaches 700 MB or so. Others have similar huge numbers. As I said, I suggest checking the report on LP out.
Please provide a valgrind log and exact instructions to reproduce. See http://techbase.kde.org/Development/Tools/Valgrind or http://valgrind.org/docs/manual/quick-start.html for some quick introduction.
Okay, I'll try. Should I upload the log as an attachment here? Reproducing this is easy. Open System Monitor or top in order to see its memory usage and start playing any track, then either wait for a track change or just click 'Next'. With every single track change you'll notice a significant increment of memory. And it keeps adding up.
Created attachment 216027 [details] Valgrind log Adding valgrind log. I tried disabling Replay Gain plugin, but it doesn't change anything.
This doesn't include leak information, so it doesn't really help. I'm not seeing a "significant increment of memory" on every track change. We do appear to be leaking a pixbuf sometimes, which should be fixed shortly.
commit 8999cca fixes that.
Oh, thanks, I'll try to test this!
commits 195c2a7, 5b281f5 and 96aa2cd fix more leaks
3dec1ff, fc1e8ca, 7ea940f and 7cdf4cd fix even more leaks..
As I've so far been unable to get any attention or reply concerning the issue from any of Ubuntu developers, despite this being the highest rated Rhythmbox bug on Ubuntu's Launchpad, I thought to myself maybe you, Jonathan, could roll out a minor release (say 2.97.1 or even 2.97.0.1) in the nearest future with these fixes in? Hopefully Ubuntu devs would do a backport from Quantal then (as they have done with 2.97). I would make a backport myself, but unfortunately the last time I messed with making Debian packages was a long time ago, like five years ago or so, therefore most of that knowledge have gone into oblivion. :)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1187.