GNOME Bugzilla – Bug 785804
gdppay : segmentation fault when use gdppay and gdpdepay
Last modified: 2018-11-03 14:11:46 UTC
This is a sample. rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! avdec_h264 ! videoconvert ! gdppay ! gdpdepay ! autovideosink ** (gst-launch-1.0:13870): CRITICAL **: gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 13870' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
Please provide a sample stream that causes this, or at least a backtrace with debug symbols.
Hi, Thanks for your reply. So I need to provide real IP address, right? Best regards, Stephen
If it's publicly available that would help, yes. Otherwise you could either provide a backtrace of all threads with debug symbols, or alternatively you can capture data from the stream and store it in a file as long as the crash is reproducible from that file.
(In reply to Sebastian Dröge (slomo) from comment #3) > If it's publicly available that would help, yes. Otherwise you could either > provide a backtrace of all threads with debug symbols, or alternatively you > can capture data from the stream and store it in a file as long as the crash > is reproducible from that file. Hi, I changed pipeline from rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! avdec_h264 ! videoconvert ! gdppay ! gdpdepay ! xvimagesink to rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! avdec_h264 ! gdppay ! gdpdepay ! videoconvert ! xvimagesink This pile can preview the window successful. when I changed codec from avdec_h264 to vaapih264, it can't work. pipeline rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! vaapih264dec ! gdppay ! gdpdepay ! vappipostproc ! vaapisink but When I close the gdp, it was fine as below, pipeline rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! vaapih264dec ! vappipostproc ! vaapisink So, could you please give me the suggestion, where is the stage I need to capture the file? Thanks, Stephen
distribution ubuntu 14.04.5 CPU i7-7700 HQ 2.8GHz dump file rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! vaapih264dec ! gdppay ! gdpdepay ! vappipostproc ! filesink location=dump.file URL--> https://drive.google.com/open?id=0B8BMRxjBsFHUTG1VWW1KTW0zVmM
I meant a file as created by > rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! vaapih264dec ! gdppay ! filesink location=whatever.gdp Something that can be loaded again later from the file to reproduce the crash.
Hi, I share the global IP. gst-launch-1.0 rtspsrc protocols=4 location=rtsp://122.116.92.9:8505/test ! rtph264depay ! h264parse ! vaapih264dec ! gdppay ..........
Hi Sebastian, I try to replace vaapih264dec to nvdec, it has the same problem, too.
bugfix: increase videoconvert between vaapih264dec and gdppay rtspsrc protocols=4 location=rtsp://ip_address ! rtph264depay ! h264parse ! vaapih264dec ! videoconvert ! video/x-raw,format=I420 ! gdppay ! gdpdepay ! videoconvert ! autovideosink
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/592.