• Sebastian Dröge's avatar
    bin: Hold the state lock while removing elements from a bin · 7f70d7a9
    Sebastian Dröge authored
    We need to take the state lock here to ensure that we're
    not currently just before setting the state of this child
    element. Otherwise it can happen that we removed the element
    here and e.g. set it to NULL state, and shortly afterwards
    have another thread set it to a higher state again as part of
    a state change for the whole bin.
    
    When adding an element to the bin this is not needed as we
    require callers to always ensure after adding to the bin that
    the new element is set to the correct state.
    7f70d7a9
Name
Last commit
Last update
common @ 59cb6781 Loading commit data...
data Loading commit data...
docs Loading commit data...
gst Loading commit data...
hooks Loading commit data...
libs Loading commit data...
m4 Loading commit data...
pkgconfig Loading commit data...
plugins Loading commit data...
po Loading commit data...
scripts Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
.gitmodules Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
ChangeLog Loading commit data...
MAINTAINERS Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README Loading commit data...
README.static-linking Loading commit data...
RELEASE Loading commit data...
TODO Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
gst-element-check-1.0.m4 Loading commit data...
gstreamer.doap Loading commit data...
meson.build Loading commit data...
meson_options.txt Loading commit data...
stamp.h.in Loading commit data...