[gstreamer-bugs] [Bug 163351] Rhythmbox/Gstreamer stops playing, starts using 100% CPU, and needs to be killed, on some OGG and Flac files.

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=163351
 GStreamer | don't know | Ver: 0.8.7





------- Additional Comments From Joseph Farmer  2005-06-11 02:24 -------
This was occurring on two different machines.  Both machines have completely
different hardware so it wasn't machine related.  Both machines are on Fedora
Core 3.  About 3 weeks ago the problem changed for the better.  Previously two
situations could occur: 50% CPU but hitting "next" in Rhythmbox would move to
the next song and things would be fine.  In other cases 100% CPU would be seen
and Rhythmbox would be unresponsive and it would have to be killed.  Both
machines do "autoupdate" via YUM and something changed.  Now there is only one
situation:  100% CPU but hitting "next" moves to the next song and CPU goes back
to normal.  This is perfectly acceptable behaviour for flaky oggs and flacs. 
Some of the CDs were scratched and I've noticed it's generally oggs and flacs
from them CDs.  Not having to "kill" Rhythmbox is much better.  It's likely that
the change from from 50% to 100% cpu is because the machine started in non-smp
mode (Hyperthreading).  I'll boot to smp this weekend and see if that is the
case.  The machine has not locked up Rhythmbox in 3 weeks now.  That is a big
change as it would lock up Rhythmbox daily before.

As it currently exists it's no longer a bug to me.  Having to kill Rhythmbox
when it hit bad Oggs was a bug.  Just having to "next" past them if fine.

Cheers. 

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.