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

[GStreamer (bugzilla.gnome.org)]

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:
  http://bugzilla.gnome.org/show_bug.cgi?id=537539

  GStreamer | gst-plugins-good | Ver: HEAD CVS
           Summary: [pulse] Rhythmbox starts using 100% of CPU time when
                    pulseaudio gets killed
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: slomo at circular-chaos.org
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Moved from http://pulseaudio.org/ticket/188:

When rhythmbox is playing through GStreamer and PulseAudio, and PulseAudio gets
killed, Rhythmbox will start eating 100% of CPU time and memory usage will grow
until the machine runs out of memory.

I submitted this first to the GNOME/Rhythmbox bugzilla as I thought this was a
Rhythmbox problem, but there they state that this would be a gst-pulse problem.
Can you comment on this?

The Rhythmbox bug report: http://bugzilla.gnome.org/show_bug.cgi?id=503126 

-----------------------------------------------------------------------------

03/04/08 12:30:23 changed by coling

Hi Fred,

I'm not seeing 100% CPU but I do get a deadlock in rhythmbox - e.g. it totally
freezes.

As pointed out by CJ on the pa ML, this deadlock I'm seeing is possibly due to
#251.

03/04/08 12:32:36 changed by coling

-----------------------------------------------------------------------------

I should clarify, that I have seem other apps exhibit high CPU and memory
eating characteristics when killing the pa server or just the stream. This
usually happens for me when the underlying ALSA driver can no longer output and
the gstreamer streams somehow just freeze in pa and sit there. I can usually
trigger this specific behaviour when suspending/resuming (about one in three
times).


-- 
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.