Intermittent video corruption in browsers with VA-API hardware decoding (Steam Deck OLED), since ~mid-2026

Abierto
  • ¿Algo no está bien?
#3,056 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, ubuntu
Área
computer-graphics, operating-systems

Línea de trabajo

The report identifies Steam Deck OLED, SteamOS 3.9.3, Mesa 26.1.2, Flatpak Chrome and Firefox, and the VA-API decode path; it does not name a source file or test. Start by checking whether the corruption reproduces with hardware decoding enabled and reviewing the amdgpu logs around an episode. Done means identifying and fixing the cause so extended YouTube playback stays clean with hardware decoding enabled.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hardware: Steam Deck OLED (Galileo, Sephiroth/Van Gogh-family APU), BIOS F7G0114
SteamOS: 3.9.3, build 20261015.100, beta channel (although problem persisted through switch from standard to beta)
Kernel: 7.2.7-valve2-1-neptune-72
System Mesa: 26.1.2 (radeonsi)
Flatpak GL runtime used by browsers: org.freedesktop.Platform.GL.default 26.2.4 (25.08 branch)
Browsers: Google Chrome 155.0.8059.84 (Flatpak), Firefox 158.0 (Flatpak)

Description

YouTube playback in Desktop Mode gets heavily distorted/corrupted at random moments during playback, then recovers. It happens in both Chrome and Firefox (slightly less often in Firefox). It started around May 2026 after a system update that had been put off for a while. It has persisted through rolling back SteamOS updates and a full factory reset.

Workaround / isolation

Turning off hardware video decoding fixes it completely:

  • Chrome: flatpak override --user --env=LIBVA_DRIVER_NAME=disabled com.google.Chrome (media-internals then shows Dav1dVideoDecoder instead of VaapiVideoDecoder)
  • Firefox: media.hardware-video-decoding.enabled=false

With software decoding, playback has been clean in testing. This points to the VA-API/VCN decode path (YouTube sends VP9 when hardware decoding is on, because Van Gogh has no AV1 hardware decode) or to the handling of the decoded frames afterward.
amdgpu 0000:04:00.0: Starting gfx_0.0.0 ring reset
amdgpu 0000:04:00.0: [gfxhub] page fault (src_id:0 ring:88 vmid:6 pasid:206)
amdgpu 0000:04:00.0: Process chrome pid 53931 thread chrome:cs0 pid 53937
amdgpu 0000:04:00.0: in page starting at address 0x000080c11078a000 from client 0x1b (UTCL2)
amdgpu 0000:04:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x006012B1
amdgpu 0000:04:00.0: Faulty UTCL2 client ID: SQC (inst) (0x9)
amdgpu 0000:04:00.0: PERMISSION_FAULTS: 0xb
amdgpu 0000:04:00.0: Ring gfx_0.0.0 reset succeeded
amdgpu 0000:04:00.0: [drm] device wedged, but no recovery needed

Most corruption episodes don't produce a kernel log entry.

Steps to reproduce

  1. Desktop Mode, Chrome or Firefox Flatpak with default settings (hardware decoding on).
  2. Play YouTube videos (1080p) for an extended period.
  3. Periodically the image becomes distorted or corrupted for a while, then recovers.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.7k
Forks
89
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ValveSoftware/SteamOS

Todos los issues de ValveSoftware/SteamOS

Issues similares

Más issues de Computer Graphics

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.