*** This bug is a duplicate of bug 1031449 ***
https://bugs.launchpad.net/bugs/1031449
** This bug has been marked a duplicate of bug 1031449
rhythmbox leaking memory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
[Expired for rhythmbox (Ubuntu) because there has been no activity for
60 days.]
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/42
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.
** Changed in: rhythmbox (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) =>
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
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
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
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
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
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 memo
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 crank
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 i
I can't be the only person seeing this bug:
28015 jmcdonag 20 0 42.3g 1.2g 16m S4 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
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 lar
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.
** Changed in: rhythmbox (Ubunt
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/Bug
15 matches
Mail list logo
