pad: Don't consider flushing pads as needing reconfiguration

Renegotiation and reconfiguration will fail because all queries
and events won't be accepted by the pad if it's flushing. In the
best case this just causes unneeded work and spurious warnings in
the debug logs, in the worst case it causes elements to fail completely.
This commit is contained in:
Sebastian Dröge 2013-06-30 18:39:03 +02:00
parent 2f78e96299
commit 948a9d2f2b

View file

@ -1400,8 +1400,13 @@ gst_pad_needs_reconfigure (GstPad * pad)
g_return_val_if_fail (GST_IS_PAD (pad), FALSE);
GST_OBJECT_LOCK (pad);
if (GST_PAD_IS_FLUSHING (pad)) {
GST_DEBUG_OBJECT (pad, "pad is flushing");
reconfigure = FALSE;
} else {
reconfigure = GST_PAD_NEEDS_RECONFIGURE (pad);
GST_DEBUG_OBJECT (pad, "peeking RECONFIGURE flag %d", reconfigure);
}
GST_OBJECT_UNLOCK (pad);
return reconfigure;
@ -1424,11 +1429,16 @@ gst_pad_check_reconfigure (GstPad * pad)
g_return_val_if_fail (GST_IS_PAD (pad), FALSE);
GST_OBJECT_LOCK (pad);
if (GST_PAD_IS_FLUSHING (pad)) {
GST_DEBUG_OBJECT (pad, "pad is flushing");
reconfigure = FALSE;
} else {
reconfigure = GST_PAD_NEEDS_RECONFIGURE (pad);
if (reconfigure) {
GST_DEBUG_OBJECT (pad, "remove RECONFIGURE flag");
GST_OBJECT_FLAG_UNSET (pad, GST_PAD_FLAG_NEED_RECONFIGURE);
}
}
GST_OBJECT_UNLOCK (pad);
return reconfigure;