[gstreamer-bugs] [Bug 537539] [pulse] Rhythmbox starts using 100% of CPU time when pulseaudio gets killed

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Fri Oct 3 09:49:57 PDT 2008

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:

  GStreamer | gst-plugins-good | Ver: HEAD CVS

Martin Olsson changed:

           What    |Removed                     |Added
                 CC|                            |mnemo at minimum.se

------- Comment #1 from Martin Olsson  2008-10-03 16:49 UTC -------
Yesterday I ran into a very very similar bug where totem started to spin 100%
CPU with uncontrolled VIRT growth. This happened immediately when I typed
"killall pulseaudio".

However, generally what happens when I play something in totem using
pulse-backend and then kill pulse is that totem GUI freezes with an empty error
messagebox (no CPU spin and no VIRT growth) so there is clearly some particular
condition which put be met for the "killall pulseaudio" to go into CPU spin

That said, I was able to get a lot of info out of gdb attached to totem when it
was spinning and that information was sufficient for wim to fix that bug.

My totem+pulse CPU spin was reported here:

See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=537539.

More information about the Gstreamer-bugs mailing list