1620821 - [Wayland] VA-API fails to initialize and content process crashes with security.sandbox.content.level less than 4

Status: RESOLVED DUPLICATE of bug 1619585

(Core :: Audio/Video: Playback, defect, P5)

Description

[Kestrel]

VA-API initializes successfully for me on Ubuntu 19.10 without crashing unless I reduce the sandbox level below 4.

security.sandbox.content.level = 4

[AVHWDeviceContext @ 0x7fb7106c4bc0] Cannot open X11 display :0.
[AVHWDeviceContext @ 0x7fb7106c4bc0] Opened VA display via DRM device /dev/dri/renderD128.
[AVHWDeviceContext @ 0x7fb7106c4bc0] libva: VA-API version 1.5.0
[AVHWDeviceContext @ 0x7fb7106c4bc0] libva: va_getDriverName() returns 0
[AVHWDeviceContext @ 0x7fb7106c4bc0] libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
[AVHWDeviceContext @ 0x7fb7106c4bc0] libva: Found init function __vaDriverInit_1_5
[AVHWDeviceContext @ 0x7fb7106c4bc0] libva: va_openDriver() returns 0
[AVHWDeviceContext @ 0x7fb7106c4bc0] Initialised VAAPI connection: version 1.5

security.sandbox.content.level < 4

[AVHWDeviceContext @ 0x7f7c4d415800] Opened VA display via X11 display :0.
[AVHWDeviceContext @ 0x7f7c4d415800] libva: VA-API version 1.5.0
[AVHWDeviceContext @ 0x7f7c4d415800] libva: va_getDriverName() returns -1
[AVHWDeviceContext @ 0x7f7c4d415800] libva: va_getDriverName() failed with unknown libva error,driver_name=(null)
[AVHWDeviceContext @ 0x7f7c4d415800] Failed to initialise VAAPI connection: -1 (unknown libva error).

Crash: bp-1ba87c4c-a475-47c4-af9c-2e6a50200307

Same crash signature as Bug 1619544.

Comment 1

[Jan Alexander Steffens [:heftig]]

I also get crashes that disappear when I either disable vaapi or reduce the sandbox level. However, in my case it's the semget function triggering the crash, e.g. bp-3c22b5e0-72e6-4c37-a28f-3c32d0200311

Sandbox: seccomp sandbox violation: pid 28604, tid 28720, syscall 64, args 1140872792 1 1974 140566631284968 0 140566182343256. Killing process.

Firefox Nightly on Arch Linux.

Comment 2

[Darkspirit]

(In reply to Jan Alexander Steffens [:heftig] from comment #1)

I also get crashes that disappear when I either disable vaapi or reduce the sandbox level. However, in my case it's the semget function triggering the crash, e.g. bp-3c22b5e0-72e6-4c37-a28f-3c32d0200311

Sandbox: seccomp sandbox violation: pid 28604, tid 28720, syscall 64, args 1140872792 1 1974 140566631284968 0 140566182343256. Killing process.

Firefox Nightly on Arch Linux.

That's bug 1619585.

Comment 4

[Darkspirit]

This crash seems to happen if Kestrel disables the sandbox instead of leaving it enabled. Is this really a duplicate?
This seemed strange:

Opened VA display via X11 display :0.