After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607571 - rtspsrc: Does not push EOS before posting an error
rtspsrc: Does not push EOS before posting an error
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.25
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-20 17:20 UTC by Chris Shoemaker
Modified: 2010-08-19 16:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chris Shoemaker 2010-01-20 17:20:53 UTC 
I'm running this pipeline:

gst-launch-0.10 -e -vm rtspsrc location=$video_url ! rtpmp4vdepay ! mpeg4videoparse ! mp4mux name=muxer ! filesink location=foo.mp4  audiotestsrc wave=silence do_timestamp=true ! faac profile=2 ! muxer.audio_0

After running successfully for a while, I disconnect the network cable, wait 60 seconds, and then reconnect the network cable.

Got Message #84 from element "rtspsrc0" (error): GstMessageError, gerror=(GstGError)(NULL), debug=(string)"gstrtspsrc.c\(3153\):\ gst_rtspsrc_loop_udp\ \(\):\ /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:\012Could\ not\ receive\ message.\ \(System\ error:\ Connection\ reset\ by\ peer\)";

ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.

Additional debug info:
gstrtspsrc.c(3153): gst_rtspsrc_loop_udp (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive message. (System error: Connection reset by peer)
Execution ended after 71939232919 ns.
Comment 1 Wim Taymans 2010-01-21 15:37:55 UTC 
It seems that it does push an EOS message in this error case.
The rule is that the error message is posted first and then the EOS is pushed.
Comment 2 Wim Taymans 2010-06-14 17:32:36 UTC 
what is the problem here again?