GNOME Bugzilla – Bug 783172
[Wayland] Traceback when using vaapih264dec and vaapisink on Intel hardware
Last modified: 2017-05-29 08:40:34 UTC
Created attachment 352718 [details] A full backtrace from gdb attached to gst-launch-1.0 Using vaapih264dec/vaapisink fails: $ LC_ALL=C gst-launch-1.0 -v filesrc location='Videofile.mp4' ! qtdemux ! h264parse ! vaapih264dec ! vaapisink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Got context from element 'vaapisink0': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayWayland\)\ vaapidisplaywayland1"; /GstPipeline:pipeline0/GstH264Parse:h264parse0.GstPad:src: caps = video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)3.1, profile=(string)high, codec_data=(buffer)0164001fffe1001c6764001facd940b427b016a0c020c800000300080015f90078c18cb001000568ebecb22c, width=(int)720, height=(int)304, framerate=(fraction)24/1, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, parsed=(boolean)true /GstPipeline:pipeline0/GstVaapiDecode_h264:vaapidecode_h264-0.GstPad:sink: caps = video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)3.1, profile=(string)high, codec_data=(buffer)0164001fffe1001c6764001facd940b427b016a0c020c800000300080015f90078c18cb001000568ebecb22c, width=(int)720, height=(int)304, framerate=(fraction)24/1, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, parsed=(boolean)true /GstPipeline:pipeline0/GstH264Parse:h264parse0.GstPad:sink: caps = video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)3.1, profile=(string)high, codec_data=(buffer)0164001fffe1001c6764001facd940b427b016a0c020c800000300080015f90078c18cb001000568ebecb22c, width=(int)720, height=(int)304, framerate=(fraction)24/1, pixel-aspect-ratio=(fraction)1/1 Redistribute latency... /GstPipeline:pipeline0/GstVaapiDecode_h264:vaapidecode_h264-0.GstPad:src: caps = video/x-raw(memory:VASurface), format=(string)NV12, width=(int)720, height=(int)304, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)24/1 /GstPipeline:pipeline0/GstVaapiSink:vaapisink0.GstPad:sink: caps = video/x-raw(memory:VASurface), format=(string)NV12, width=(int)720, height=(int)304, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)24/1 Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock wl_surface@7: error 2: Failed to create a texture for surface 7: Unsupported buffer format 12760 ERROR: from element /GstPipeline:pipeline0/GstVaapiSink:vaapisink0: Internal error: could not render surface Additional debug info: gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPipeline:pipeline0/GstVaapiSink:vaapisink0 Execution ended after 0:00:00.002143907 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Caught SIGSEGV
+ Trace 237524
Installed software versions: gstreamer1-plugins-good-1.12.0-1.fc26.x86_64 gstreamer1-vaapi-1.12.0-1.fc26.x86_64 libva-1.8.2-1.fc26.x86_64 libva-intel-driver-1.8.2-1.fc26.x86_64 glib2-2.52.2-2.fc26.x86_64 $ vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Ironlake Desktop - 1.8.2 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc Additional info: Same pipeline works fine if replacing "vaapisink" by "fakesink".
(bugzilla broke the Traceback, but if you click on the link you'll see the original text) $ lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12)
Running the same pipeline under X11 works fine.
*** This bug has been marked as a duplicate of bug 775698 ***