[Bug 643087] pulsesink: deadlock in gst_pulseringbuffer_open_device

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=643087
  GStreamer | gst-plugins-good | git

--- Comment #22 from Stefan Kost (gstreamer, gtkdoc dev) <ensonic at sonicpulse.de> 2011-02-28 08:35:30 UTC ---
(In reply to comment #21)
> To clarify, the deadlock can only be reproduced when you have at least two
> pulsesink elements. The reason that I can easily reproduce it is because I have
> a HTML test case with two <video> elements using the same slow-loading data
> source. This creates two GStreamer pipelines which are fed with the same data
> at (almost) the same time, so the two pulsesink elements will be created at
> (almost) the same time.

Yes, I understand that. But the pa_threaded_mainloop was in the *class*
structure before. That means all instances where already sharing the same
instance.

The chain of chainged that lead to the current setup started with the patch
http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=69a397c32f4baf07a7b2937c610f9e8f383e9ae9
in bug #624338

I was fixing that with
http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=f62dc6976b611384c98efb37d407b5299daf8c17
some discussion in bug #628996

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