GNOME Bugzilla – Bug 712542
Crash possibly due to faulty/incomplete caps in udpsrc
Last modified: 2015-01-24 09:03:30 UTC
Running: gst-launch-1.0.exe -v rtpbin name=rtpbin filesrc location=Sample.mp4 ! qtdemux name=d ! queue ! h264parse ! rtph264pay config-interval=1 ! rtpbin.send_rtp_sink_0 rtpbin.send_rtp_src_0 ! udpsink host=127.0.0.1 port=5000 rtpbin.send_rtcp_src_0 ! udpsink host=127.0.0.1 port=5001 sync=false async=false d. ! queue ! aacparse ! rtpmp4apay ! rtpbin.send_rtp_sink_1 rtpbin.send_rtp_src_1 ! udpsink host=127.0.0.1 port=5002 rtpbin.send_rtcp_src_1 ! udpsink host=127.0.0.1 port = 5003 sync=false async=false udpsrc port=5007 ! rtpbin.recv_rtcp_sink_1 --gst-debug=rtpbin:7 and then in another window: gst-launch-1.0.exe -v rtpbin name=rtpbin udpsrc caps="application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264, payload=(int)96, ssrc=(uint)2987805418, timestamp-offset=(uint)2011697778, seqnum-offset=(uint)53221" port=5000 ! rtpbin.recv_rtp_sink_0 rtpbin. ! rtph264depay ! avdec_h264 ! autovideosink udpsrc port=5001 ! rtpbin.recv_rtcp_sink_0 rtpbin.send_rtcp_src_0 ! udpsink host=127.0.0.1 port=5005 sync=false async=false udpsrc caps="application/x-rtp, media=(string)audio, clock-rate=(int)44100, encoding-name=(string)MP4A-LATM" port = 5002 ! rtpbin.recv_rtp_sink_1 rtpbin. ! rtpmp4adepay ! decodebin ! autoaudiosink udpsrc port=5003 ! rtpbin.recv_rtcp_sink_1 rtpbin.send_rtcp_src_1 ! udpsink host=127.0.0.1 port=5007 sync=false async= false --gst-debug=*udp*:5 causes gst-launch-1.0.exe to crash. This might be due to faulty/incomplete caps set on udpsrc in the first udpsrc mentioned in the second window. Video used was http://www.auby.no/files/video_tests/h264_720p_mp_3.1_3mbps_aac_shrinkage.mp4 (that I renamed to Sample.mp4).
Which version are you using? I can't reproduce with either the latest 1.0.x, or 1.2.x or git master.
(In reply to comment #1) > Which version are you using? I can't reproduce with either the latest 1.0.x, > or 1.2.x or git master. Hi Pzkfw, I am closing this bug report as no updated information has been provided. Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.