basesrc: No need to stop flushing in start_complete
authorNicolas Dufresne <nicolas.dufresne@collabora.com>
Wed, 7 Mar 2018 16:16:00 +0000 (11:16 -0500)
committerNicolas Dufresne <nicolas.dufresne@collabora.com>
Thu, 8 Mar 2018 01:03:56 +0000 (20:03 -0500)
commit12c5d903c9cf80d9365d57b4643fef9f57aa4d60
tree870c8ddad4cf1072cacd712cc9cc84be73f30220
parentf204b57fa54447d7d0052cd96f0fc5cb76016af6
basesrc: No need to stop flushing in start_complete

The flushing state is handled a bit differently, there is no need
to stop flushing in start_complete. This would other result in
unlock_stop being called without unlock_start.

Unlike what the old comment says, there is no need to take the live
lock here, we are still single threaded at this point (app thread
or the state change thread). Also, we will wait for playing state
in create/getrange, no need to do that twice.

https://bugzilla.gnome.org/show_bug.cgi?id=794149
libs/gst/base/gstbasesrc.c