[gstreamer-bugs] [Bug 630997] New: Socket error causes file created by 'filesink' element to be invalid while EOS on SIGINT does not...

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=630997
  GStreamer | gstreamer (core) | git

           Summary: Socket error causes file created by 'filesink' element
                    to be invalid while EOS on SIGINT does not...
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: rob.krakora at messagenetsystems.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: Unversioned Enhancement


When I execute this pipeline from the command line...

 gst-launch -e rtspsrc location=rtsp://192.168.1.211:8109/camera.sdp !
rtpmp4vdepay ! mpeg4videoparse ! mp4mux ! filesink location=myfile

...and send a SIGINT to the process I get a file that is playable because I
specified the '-e' which indicates that EOS on shutdown.

However, if I execute the same pipeline from the command line and remove the
RTSP server (i.e. force a socket error) the process exits without performing an
EOS on shutdown.  A quick look at the code in "gst-launch.c" confirmed my
suspicion that EOS on shutdown is only performed on a SIGINT.  What if my
application has recorded valuable video data and the network goes down, does
this mean I have lost all of that data since the file will not be viewable due
to the absence of EOS on shutdown processing on anything that is not a SIGINT?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.