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

未关闭
#3,056 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
40/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
linux, ubuntu

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
没有语言数据
星标
2.7k
派生
89
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ValveSoftware/SteamOS 的其他 Issue

查看 ValveSoftware/SteamOS 的全部 Issue

相似的 Issue

更多 Computer Graphics Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。