GNOME Bugzilla – Bug 142588
[threads] if all elements have been removed from a bin, should it's state not be set to GST_STATE_NULL
Last modified: 2005-01-31 15:43:48 UTC
I encountered a problem with a GstThread which I emptied during PAUSED state, when I removed it from the main pipeline...the app core dumped due to freeing a locked mutex. The mutex gets unlocked during state change to NULL. I tried changing state to NULL before removing it from the main pipeline, but it didnt change the state. Ideally the gst_bin_remove should check if after removing, a bin is empty and if it is it should change state to NULL.
*** Bug 147000 has been marked as a duplicate of this bug. ***
Zaheer, threadg passes with no problems here. As for your original request, bins can have states independent of their contained children. Bins can even be elements themselves. It's non-sensical to change rules specifically for bins. I see your point, but I think they should be able to be in a non-NULL state themselves. We have gst_bin_synchronize_children_state() to get kids even. If you agree, we can re-enable threadg and close this bug.
Hm, what I'm saying is crap, empty bins already set themselves to NULL state... Ohwell, I stand corrected then. We should re-enable threadg (#123775 has a patch to do that) and close this bug.
Done.