[Bug 744420] New: splitmuxsink - Deadlock on while starting 2nd fragment on function gst_element_sync_state_with_parent

[bugzilla at gnome.org]

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

            Bug ID: 744420
           Summary: splitmuxsink - Deadlock on while starting 2nd fragment
                    on function gst_element_sync_state_with_parent
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: memento1987 at interia.pl
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 296710
  --> https://bugzilla.gnome.org/attachment.cgi?id=296710&action=edit
Last logs before deadlock

I tried to use new GStreamer element - splitmuxsink with RTSP streams bug meet
problem with deadlock.

My pipeline: 
GST_DEBUG=splitmuxsink:5 gst-launch-1.0 rtspsrc
location=rtsp://192.168.2.5:8554/h264ESVideoTest ! rtph264depay ! h264parse  !
splitmuxsink location=file%02d.mp4 max-size-time=10000000000

RTSP stream is slamtv60.ts stream from Live555 RTSP generator. I also tested
with live webcam RTSP stream created with VLC and met the same problem. 

Vlc command which I used for generation live RTSP stream: 
cvlc v4l2:///dev/video0 --sout
"#transcode{vcodec=h264,vb=0,scale=0,acodec=mp4a,ab=128,channels=2,samplerate=44100}:rtp{sdp='$RTSP_URL'}"
&

For above pipeline and both of the above stream first 10 second fragment is
captured properly to file file00.mp4, but there is deadlock before capturing
second fragment.

I did quick investigation and found that deadlock happens in following
function:
gst_element_sync_state_with_parent (splitmux->active_sink);
in file gstsplitmuxsink.c:675 

Below I attach image of last visible logs from above pipeline before deadlock
occured (notice that I added additional ERROR messages in order to find out
where is deadlock):
http://oi61.tinypic.com/nmntrp.jpg

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