tree 870c8ddad4cf1072cacd712cc9cc84be73f30220
parent f204b57fa54447d7d0052cd96f0fc5cb76016af6
author Nicolas Dufresne <nicolas.dufresne@collabora.com> 1520439360 -0500
committer Nicolas Dufresne <nicolas.dufresne@collabora.com> 1520471036 -0500

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