Rhythmbox starts using 100% of CPU time when pulseaudio gets killed

[fhimpe]

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

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

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

[slomo]

As gst-pulse has now moved to gst-plugins-good the bug is now here: http://bugzilla.gnome.org/show_bug.cgi?id=537539