Subject: Re: bug#63197: video acceleration/libva segfaults caused by stale mesa shader cache

From: Maxim Cournoyer <[email-masked]>
Date: Thu, 25 Apr 2024 14:47:52 -0400

Hi,

Maxim Cournoyer <[email-masked]> writes:

> Hi,
>
> After reinstalling someone's desktop which has support for VA-API,
> 'vainfo' from 'libva-utils' would consume all the memory then crash.
> Other applications relying on libva would crash as well, e.g. ffmpeg (or
> its users, such as vlc/jami).  Here's a sample output from VLC:
>
> vlc received_605209834855384.mp4 
> VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
> [000000000109d770] main libvlc: Lancement de vlc avec l'interface par défaut. Utiliser « cvlc » pour démarrer VLC sans interface.
> libva info: VA-API version 1.17.0
> libva info: Trying to open /gnu/store/9pypr3c3y379shbwm9ilb4pik9mkfd83-mesa-22.2.4/lib/dri/radeonsi_drv_video.so
> libva info: Found init function __vaDriverInit_1_17
> Erreur de segmentation

The same issue was reproduced with vlc and Totem after the latest
upgrades, which brought mesa from version 23 to 24.  The same solution:

--8<---------------cut here---------------start------------->8---
$ rm -rf ./.cache/mesa_shader_cache
--8<---------------cut here---------------end--------------->8---

still works.

I've sent upstream a fresh snapshot of the 23 -> 24 corrupted cache [0].

[0]  https://gitlab.freedesktop.org/mesa/mesa/-/issues/8937#note_2388471

-- 
Thanks,
Maxim