26.2.0 segfault with gstreamer 1.0, vaapi
Moderator: trava90
Forum rules
If your question is about general use of the browser and not specific to Linux, then please use the General Support board.
If your question is about general use of the browser and not specific to Linux, then please use the General Support board.
26.2.0 segfault with gstreamer 1.0, vaapi
Just upgraded to 26.2.0, and installed gstreamer1.0 good, bad & ugly packages to test out youtube.
However, I got a crash as soon as it tried to load an HTML5 video.
So, I ran in terminal for additional output and got:
libva info: VA-API version 0.36.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_36
libva info: va_openDriver() returns 0
** (pale moon:4814): CRITICAL **: gst_video_meta_map_vaapi_memory: assertion 'GST_VAAPI_IS_VIDEO_ALLOCATOR(mem->parent_instance. allocator)' failed
Segmentation fault
I removed gstreamer1.0-vaapi and the segfault was fixed.
But it would be nice if I could use vaapi.
Details of my system:
Debian 8 (x64)
CPU is Intel(R) Core(TM) i5-4210U
GPU at the time was Intel® HD Graphics 4400, although this is a bumblebee system that can use nvidia as well.
Let me know if there's any more info I can provide, tracing perhaps. I'm not familiar with logging options for palemoon.
However, I got a crash as soon as it tried to load an HTML5 video.
So, I ran in terminal for additional output and got:
libva info: VA-API version 0.36.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_36
libva info: va_openDriver() returns 0
** (pale moon:4814): CRITICAL **: gst_video_meta_map_vaapi_memory: assertion 'GST_VAAPI_IS_VIDEO_ALLOCATOR(mem->parent_instance. allocator)' failed
Segmentation fault
I removed gstreamer1.0-vaapi and the segfault was fixed.
But it would be nice if I could use vaapi.
Details of my system:
Debian 8 (x64)
CPU is Intel(R) Core(TM) i5-4210U
GPU at the time was Intel® HD Graphics 4400, although this is a bumblebee system that can use nvidia as well.
Let me know if there's any more info I can provide, tracing perhaps. I'm not familiar with logging options for palemoon.
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
Which version of vaapi are you using? I don't think that this is a Pale Moon bug, but rather a bug in vappi, which was fixed in (I believe) version 0.5.9. Here's the vaapi commit: https://gitorious.org/vaapi/gstreamer-vaapi/commit/9cad85a93649b1b6da6084b85f807139e84a41a4?p=vaapi:gstreamer-vaapi.git;a=commit;h=9cad85a93649b1b6da6084b85f807139e84a41a4
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
I am using 0.5.9, so this fix should be included judging from this list: https://gitorious.org/vaapi/gstreamer-v ... tags/0.5.9
Debian 8's version number is "0.5.9-2"
Debian 8's version number is "0.5.9-2"
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
Which version of libva do you have installed? Versions prior to 1.3.0 can cause crashes like this as well.
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
It looks like I have 1.4.1 for all installed,
spicard@SW3000:~$ sudo aptitude versions libva | grep "^i" -B 1
Package libva-dev:
id 1.4.1-1 stable 500
--
Package libva-drm1:
i A 1.4.1-1 stable 500
--
Package libva-egl1:
i 1.4.1-1 stable 500
--
Package libva-glx1:
i A 1.4.1-1 stable 500
--
Package libva-tpi1:
i 1.4.1-1 stable 500
--
Package libva-wayland1:
i A 1.4.1-1 stable 500
--
Package libva-x11-1:
i A 1.4.1-1 stable 500
--
Package libva1:
i A 1.4.1-1 stable 500
There's a lot of libva prefixed packaged though. Could there be any missing packages causing the crash?
spicard@SW3000:~$ sudo aptitude versions libva | grep "^i" -B 1
Package libva-dev:
id 1.4.1-1 stable 500
--
Package libva-drm1:
i A 1.4.1-1 stable 500
--
Package libva-egl1:
i 1.4.1-1 stable 500
--
Package libva-glx1:
i A 1.4.1-1 stable 500
--
Package libva-tpi1:
i 1.4.1-1 stable 500
--
Package libva-wayland1:
i A 1.4.1-1 stable 500
--
Package libva-x11-1:
i A 1.4.1-1 stable 500
--
Package libva1:
i A 1.4.1-1 stable 500
There's a lot of libva prefixed packaged though. Could there be any missing packages causing the crash?
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
We've received other reports of oddities when using gstreamer-vaapi. For now, I'd say the best solution is to just not use it.
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
I installed gstreamer-vaapi on my system, and the results were terrible. YouTube wouldn't even play the video, and CPU usage jumped over 10% higher than normal when on YouTube (and no video was playing!).trava90 wrote:We've received other reports of oddities when using gstreamer-vaapi. For now, I'd say the best solution is to just not use it.
So at this point in time, Pale Moon should be considered incompatible with gsteamer-vaapi.
Re: 26.2.0 segfault with gstreamer 1.0, vaapi
Moving this to the Linux board. I don't think we can do much about the interaction of gstreamer with vaapi from the browser side.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss


Re: 26.2.0 segfault with gstreamer 1.0, vaapi
Oh well, thanks for looking into it.trava90 wrote:I installed gstreamer-vaapi on my system, and the results were terrible. YouTube wouldn't even play the video, and CPU usage jumped over 10% higher than normal when on YouTube (and no video was playing!).trava90 wrote:We've received other reports of oddities when using gstreamer-vaapi. For now, I'd say the best solution is to just not use it.
So at this point in time, Pale Moon should be considered incompatible with gsteamer-vaapi.