all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 63197@debbugs.gnu.org
Subject: bug#63197: video acceleration/libva segfaults caused by stale mesa shader cache
Date: Mon, 26 Jun 2023 12:21:20 -0400	[thread overview]
Message-ID: <87r0py19fj.fsf@gmail.com> (raw)
In-Reply-To: <878rci2y6u.fsf@xelera.eu> (Giovanni Biscuolo's message of "Sat,  17 Jun 2023 12:14:01 +0200")

Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

[...]

>>> ...or apply a patch to rename "~/.cache/mesa_shader_cache" to
>>> "~/.cache/mesa<version>_shader_cache"
>>
>> That's another good idea.
>
> I was just doing guesswork but the bug caused by this mesa upgrade
> smells like a binary incompatibility between two versions (or just major
> versions)... so a versioned shader cache makes sense to me
>
> I'm not able to propose (I mean to code) such a patch, anyway
>
> Anyway, users should know that they have to periodically clean unused
> shader caches, since from what I read on the net the shader cache tends
> to really /explode/ in terms of size, in some cases
>
>>> Alternatively, we should find a way to make Guix users aware of this
>>> kind of problems and possible workarounds they can apply (it's not
>>> related to this specific bug)
>>
>> I would rather pursue the other above options you suggest, so that it
>> doesn't happen in the first place!

I've ping'd upstream with
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8937#note_1975560.
Let's see what they say!

-- 
Thanks,
Maxim




  reply	other threads:[~2023-06-26 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  2:42 bug#63197: video acceleration/libva segfaults caused by stale mesa shader cache Maxim Cournoyer
2023-05-01  2:58 ` Maxim Cournoyer
2023-06-15 13:49   ` Giovanni Biscuolo
2023-06-17  0:36     ` Maxim Cournoyer
2023-06-17 10:14       ` Giovanni Biscuolo
2023-06-26 16:21         ` Maxim Cournoyer [this message]
2024-04-25 18:47 ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0py19fj.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=63197@debbugs.gnu.org \
    --cc=g@xelera.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.