'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

Marc lorenzo75 at freenet.de
Wed Jan 18 18:38:58 UTC 2017


Hello,
I built up a pipeline which does HDMI output, encode and save to file and
stream via network. 

gst-launch-1.0 v4l2src device=/dev/video1 io-mode=4 !
'video/x-raw,format=(string)YUY2,width=800,height=600,framerate=(fraction)30/1'
! vpe ! 'video/x-raw, format=(string)NV12, width=(int)1920,
height=(int)1080' ! tee name=t ! queue ! ducatimpeg4enc ! mpeg4videoparse !
mpegtsmux ! tee name=q ! queue ! filesink location=/home/root/video.mp4 q. !
queue ! udpsink host=192.168.3.147 port=5555 sync=false t. ! queue ! kmssink
scale=false -v -e

The pipeline runs and from time to time there are critical errors. And in
the end, the pipeline aborts.

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:2528): CRITICAL **: gst_fd_memory_get_fd: assertion
'GST_IS_FD_ALLOCATOR (mem->allocator)' failed
handling interrupt.
Interrupt: Stopping pipeline ...
EOS on shutdown enabled -- Forcing EOS on the pipeline
^CWaiting for EOS...
Got EOS from element "pipeline0".
EOS received - stopping pipeline...
Execution ended after 0:03:56.377953895
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...


What does this error mean? I had the same error with other pipeline
configurations too.

Thanks in advance and have a nice day

Marc




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/GST-IS-FD-ALLOCATOR-mem-allocator-failed-tp4681543.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list