** Bug watch added: GNOME Bug Tracker #589062
http://bugzilla.gnome.org/show_bug.cgi?id=589062
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=589062
Importance: Unknown
Status: Unknown
--
Rhythmbox takes 420MB of RAM for playing jamendo
*** This bug is a duplicate of bug 328008 ***
https://bugs.launchpad.net/bugs/328008
** This bug has been marked a duplicate of bug 328008
Rhythmbox overloads memory with Jamendo
--
Rhythmbox takes 420MB of RAM for playing jamendo
https://bugs.launchpad.net/bugs/372687
You received this
*** This bug is a duplicate of bug 328008 ***
https://bugs.launchpad.net/bugs/328008
** Changed in: rhythmbox
Status: Unknown = New
--
Rhythmbox takes 420MB of RAM for playing jamendo
https://bugs.launchpad.net/bugs/372687
You received this bug notification because you are a member
The changelog for rhythmbox 0.12.1 contains Greatly reduced memory
usage when accessing Jamendo catalog. Does using this version (or later
version) solve the problem?
--
Rhythmbox takes 420MB of RAM for playing jamendo
https://bugs.launchpad.net/bugs/372687
You received this bug notification
OK. I started
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log rhythmbox
I click jamendo
I waited a few hours since the catalog loads (without valgrind, it takes
a few minutes)
I filtered by genre
I started a
OK. I started
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log rhythmbox
I click jamendo
I waited a few hours since the catalog loads (without valgrind, it takes
a few minutes)
I filtered by genre
I started a
the valgrind logs are not really useful there, that should rather be
sent the software writters on http://bugzilla.gnome.org by somebody
having the issue
--
Rhythmbox takes 420MB of RAM for playing jamendo
https://bugs.launchpad.net/bugs/372687
You received this bug notification because you are
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in:
