[gstreamer-bugs] [Bug 507527] Mixer eats 100% cpu when audio device goes away

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=507527
  GStreamer | gst-plugins-base | 0.10.x

--- Comment #13 from Alex Riesen <raa.lkml at gmail.com> 2010-10-03 10:36:35 UTC ---
Created an attachment (id=171619)
 View: https://bugzilla.gnome.org/attachment.cgi?id=171619
 Review: https://bugzilla.gnome.org/review?bug=507527&attachment=171619

A crude workaround to avoid looping on removed mixer device

This helps the case. The gstreamer monitor task does not loop uselessly
polling the hangup device anymore. But it really is not a good fix for
the real problem: the users of the gstreamer's mixer interface must
somehow get notified that the mixer is not good anymore to act on that.

P.S. the strange "if (!mixer->available) nfds = 0;" is so strange to satisfy
the debian patch queue. The patch which conflicted made a lot of sense to
me (missing mutex unlock) so I tried to keep it applicable (just in case
distributions monitor the bug better than gstreamer developers).

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.