[Gstreamer-bugs] [Bug 142588] New: - if all elements have been removed from a bin, should it's state not be set to GST_STATE_NULL

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=142588
GStreamer | gstreamer (core) | Ver: HEAD CVS

           Summary: if all elements have been removed from a bin, should
                    it's state not be set to GST_STATE_NULL
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-maint at bugzilla.gnome.org
        ReportedBy: zaheerabbas at merali.org
         QAContact: gstreamer-maint at bugzilla.gnome.org


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.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.