webrtcbin/transportreceivebin: Use actual pad blocks instead of an additional GCond...
authorSebastian Dröge <sebastian@centricular.com>
Thu, 6 Feb 2020 12:24:41 +0000 (14:24 +0200)
committerGStreamer Merge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Tue, 11 Feb 2020 00:49:51 +0000 (00:49 +0000)
commitf8fa71da27dd2619a509cfee585666db7627015b
tree63f1e1292c5b8c6bec8fc4495ea77b294d9b59cd
parent1ecb27f221d800b203b74052d4f1d21a31a5eb65
webrtcbin/transportreceivebin: Use actual pad blocks instead of an additional GCond for blocking pads

Using a GCond can easily lead to deadlocks and only duplicates the
waiting code from gstpad.c in the best case.

In this case it actually could lead to a deadlock if both RTP and RTCP
were waiting. Only one of them would be woken up because g_cond_signal()
was used instead of g_cond_broadcast().
ext/webrtc/transportreceivebin.c
ext/webrtc/transportreceivebin.h