[Bug 768482] New: shmsrc: stopping shmsrc after socket failure hangs on READY

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=768482

            Bug ID: 768482
           Summary: shmsrc: stopping shmsrc after socket failure hangs on
                    READY
    Classification: Platform
           Product: GStreamer
           Version: 1.8.1
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: marcin at saepia.net
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

I have a bin that contains shmsrc and capsfilter.

I intercept messages in the bin by overriding handle_message.

If socket from which shmsrc reads is unexpectedly closed I receive an error
message in handle_message sent from streaming thread.

I initiate procedure to remove such bin from the pipeline. I set state to NULL,
and it never reaches NULL.

This is the log with loglevel *:4

0:00:05.322485951 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2316:gst_bin_element_set_state:<capsfilter> current PLAYING pending
VOID_PENDING, desired next PAUSED
0:00:05.322575249 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2372:gst_element_continue_state:<capsfilter> completed state
change to PAUSED
0:00:05.322586658 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2277:_priv_gst_element_state_changed:<capsfilter> notifying about
state-changed PLAYING to PAUSED (VOID_PENDING pending)
0:00:05.322602931 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2764:gst_bin_change_state_func:<Media.Input.Stream.Test-123> child
'capsfilter' changed state to 3(PAUSED) successfully
0:00:05.322677682 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2316:gst_bin_element_set_state:<source> current PLAYING pending
VOID_PENDING, desired next PAUSED
0:00:05.322724705 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2372:gst_element_continue_state:<source> completed state change to
PAUSED
0:00:05.322734623 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2277:_priv_gst_element_state_changed:<source> notifying about
state-changed PLAYING to PAUSED (VOID_PENDING pending)
0:00:05.322755322 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2764:gst_bin_change_state_func:<Media.Input.Stream.Test-123> child
'source' changed state to 3(PAUSED) successfully
0:00:05.322774913 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2347:gst_element_continue_state:<Media.Input.Stream.Test-123>
committing state from PLAYING to PAUSED, pending NULL, next READY
0:00:05.322791096 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2277:_priv_gst_element_state_changed:<Media.Input.Stream.Test-123>
notifying about state-changed PLAYING to PAUSED (NULL pending)
0:00:05.322851563 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2354:gst_element_continue_state:<Media.Input.Stream.Test-123>
continue state change PAUSED to READY, final NULL
0:00:05.323275010 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2316:gst_bin_element_set_state:<capsfilter> current PAUSED pending
VOID_PENDING, desired next READY
0:00:05.323350698 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2372:gst_element_continue_state:<capsfilter> completed state
change to READY
0:00:05.323394320 11568      0x20118f0 INFO              GST_STATES
gstelement.c:2277:_priv_gst_element_state_changed:<capsfilter> notifying about
state-changed PAUSED to READY (VOID_PENDING pending)
0:00:05.323412442 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2764:gst_bin_change_state_func:<Media.Input.Stream.Test-123> child
'capsfilter' changed state to 2(READY) successfully
0:00:05.323424213 11568      0x20118f0 INFO              GST_STATES
gstbin.c:2316:gst_bin_element_set_state:<source> current PAUSED pending
VOID_PENDING, desired next READY

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.