I've also noticed this, in my case it's now on 900Mb consumption, I haven't
noticed till now because I have 8Gb of RAM.
I use Ubuntu x64, 9.04, rhythmbox that came installed with Ubuntu,0.12.0.
--
Possible memory leak
https://bugs.launchpad.net/bugs/58372
You received this bug notification
do you still get that problem with the new versions of the package?
--
Possible memory leak
https://launchpad.net/bugs/58372
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Actually, no, it seems to be fixed in Edgy.
--
Possible memory leak
https://launchpad.net/bugs/58372
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
thank you for the reply, marking fixed then
** Changed in: rhythmbox (Ubuntu)
Status: Needs Info = Fix Released
--
Possible memory leak
https://launchpad.net/bugs/58372
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug. What version of Ubuntu and rhythmbox do you use? Do
you play local files only? CD? Do you iconify it? Do you have a change
to memory use after an hour by example?
** Changed in: rhythmbox (Ubuntu)
Importance: Untriaged = Low
Assignee: (unassigned) = Ubuntu Desktop
If you could attach the output generated from running valgrind (see
https://wiki.ubuntu.com/Valgrind) when you start rhythmbox to when you
see the memory usage change significantly, that may be of some help once
you've narrowed down how you're using rhythmbox.
--
Possible memory leak
Rhythmbox 0.9.3.1 on Dapper. I play only local files (mp3s some ogg)
usually, although I do have the DAAP sharing option turned on and there
are a fair amount of people on my network. It stays iconified in the
tray for most of the time.
I will now start Valgrind and hopefully will have
Ok, so that didn't go as planned, because rhythmbox isn't actually
usable under valgrind. I guess I shouldn't be suprised. It did however
find some errors, so lets see if I this log is useful. If its not, I'll
leave it up overnight or something.
--
Possible memory leak
