• Edward Hervey's avatar
    decodebin3: Make input activation "atomic" · e15531bb
    Edward Hervey authored
    When adding inputs dynamically, we need to make sure the new parsebin are
    added *and* activated by the same thread (by taking the state change lock).
    
    The rationale for this is that the calling thread might be an upstream streaming
    thread and when activating parsebin it might call back upstream. If we don't use
    the same thread (ex: when the application does a state change on decodebin3
    between the moment we add parsebin to decodebin3 and we synchronize the state of
    parsebin) then we would end up in different threads trying to take upstream
    recursive locks.
    
    Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/-/merge_requests/932>
    e15531bb
Name
Last commit
Last update
docs Loading commit data...
ext Loading commit data...
gst Loading commit data...
gst-libs Loading commit data...
hooks Loading commit data...
po Loading commit data...
scripts Loading commit data...
subprojects Loading commit data...
sys Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
ChangeLog Loading commit data...
MAINTAINERS Loading commit data...
NEWS Loading commit data...
README Loading commit data...
README.static-linking Loading commit data...
RELEASE Loading commit data...
REQUIREMENTS Loading commit data...
gst-plugins-base.doap Loading commit data...
meson.build Loading commit data...
meson_options.txt Loading commit data...