rhythmbox is consuming a lot of CPU resources

An attachment is file retreived with command

rhythmbox -d 2>rhythmbox.debug

It starts to overuse CPU when playing track only.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Actually, I have experienced the same issue with several media players including Rhythmbox and Banshee. Sometimes the player uses 100% CPU only when playing a file. The CPU usage goes down when pausing. Restarting the player usually "fixes" the problem. Might be a bug in gstreamer..?

Agree, I have the same problem with Banshee.

On Tue, Nov 3, 2009 at 9:36 AM, Johannes H. Jensen <email address hidden>wrote:

> Actually, I have experienced the same issue with several media players
> including Rhythmbox and Banshee. Sometimes the player uses 100% CPU only
> when playing a file. The CPU usage goes down when pausing. Restarting
> the player usually "fixes" the problem. Might be a bug in gstreamer..?
>
> --
> rhythmbox is consuming a lot of CPU resources
> https://bugs.launchpad.net/bugs/451171
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Problem seems to be solved with latest Karmic gstreamer update. CPU usage is now never more than 3%.

For me the player starts consuming all the CPU resources immediately after playing song started. Earlier this moment was more or less random. This is true for rhythmbox and banshee.
Ubuntu Karmic, up-to-date.

Thank you for sending the bug to GNOME

Any change to get this issue solved?
Thanks.

Same problem here

happening to me too, karmic up-to-date. Getting from all sources (multiverse).

Same here, fully up to date, except the issue is intermittent for me.

I can be listening through a list of MP3s on shuffle, pause to make or take a call, and then resume, and sometimes (not all), full CPU consumption.

I can then pause, CPU consumption stops, play, and sometimes, not all, it can resume playing without maxxing out CPU.

Also of note is the images for play, forward, rewind, disappeared.

Errors that I found running rhythmbox in GDB:
 for stock: Unable to load image-loading module: /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so: /usr/lib/librsvg-2.so.2: cannot read file data: Bad address
[Thread 0x7fffd6252910 (LWP 16351) exited]

(rhythmbox:16333): Gtk-WARNING **: Error loading theme icon 'gtk-media-previous-ltr' for stock: Unable to load image-loading module: /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so: /usr/lib/librsvg-2.so.2: cannot read file data: Bad address

(rhythmbox:16333): Gtk-WARNING **: Error loading theme icon 'gtk-media-next-ltr' for stock: Unable to load image-loading module: /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so: /usr/lib/librsvg-2.so.2: cannot read file data: Bad address

(rhythmbox:16333): Gtk-WARNING **: Error loading theme icon 'gtk-media-next-ltr' for stock: Unable to load image-loading module: /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so: /usr/lib/librsvg-2.so.2: cannot read file data: Bad address

[New Thread 0x7fffd6252910 (LWP 16352)]
[New Thread 0x7fffd5a51910 (LWP 16353)]
[New Thread 0x7fffd5250910 (LWP 16354)]
[Thread 0x7fffd5250910 (LWP 16354) exited]
[Thread 0x7fffd6252910 (LWP 16352) exited]
[Thread 0x7fffd5a51910 (LWP 16353) exited]
[Thread 0x7fffd6a53910 (LWP 16350) exited]
[Thread 0x7fffe051b910 (LWP 16348) exited]
[New Thread 0x7fffe051b910 (LWP 16355)]
[New Thread 0x7fffd6a53910 (LWP 16356)]
[New Thread 0x7fffd5a51910 (LWP 16357)]

the new comment svg warnings are weird, what architecture do you use?

x86_64

2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux

I think the svg errors are related to something else going wrong, as they are the icons - the issue this bug relates to, is the CPU consumption. With or without the svg errors, the CPU consumption peaks.

I've now installed the extra codec packs for bad, ugly, etc.. and I'll test those and see what happens, but I doubt they'll be it.

- Nope, still does it.