Re: [PATCH v2 0/1] MR1278: winegstreamer: Do not destroy condition variables when a thread is waiting on them.

[Zebediah Figura (＠zfigura)]

> > This bothers me, actually, because in theory gstreamer's multiqueue should prevent this. It's designed to try to buffer streams evenly, but if one stream is getting starved it *should* allow to increase the buffering limits on the others to prevent a deadlock. I think we should investigate why this isn't working correctly.
>
> Maybe the answer is trivial: soon after `Shutdown()` is called, `gst_element_set_state(GST_STATE_NULL)` is called, and I guess it's totally reasonable that after that GStreamer stops sending samples.

I don't understand, this seems orthogonal to the problem you're describing, where refusing to read from one stream can starve the other?