From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] update mesa
Date: Thu, 07 Dec 2023 04:40:09 +0100 [thread overview]
Message-ID: <20231207034009.x8G9Hd08GWs5QnXRIG5hO9wgHAL7hEnUVs0icmAZiwI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46246@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Closed issue by darkralts on void-packages repository
https://github.com/void-linux/void-packages/issues/46246
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 AuthenticAMD notuptodate rrrmFFFFFF
### Package(s) Affected
mesa-23.1.3_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/ValveSoftware/Fossilize/issues/230#issuecomment-1712695949
as you can see here, mesa has some bugs with steam because it is outdated and makes steam almost unusable due to it eating all the ram.
### Expected behaviour
the game to open normally and to pre cache vulkan shaders without consuming your ram
### Actual behaviour
when you open a game it wil process vulkan shaders and a "fossilize_replay" will start using all your ram until it crashes.
### Steps to reproduce
1. open a game on steam with vulkan shaders pre caching enabled
2. wait for it to start caching
3. watch "fossilize_replay" in task manager and check how much ram it is using
4. your pc may crash
prev parent reply other threads:[~2023-12-07 3:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 14:14 [ISSUE] " darkralts
2023-09-26 0:20 ` zlice
2023-10-05 17:02 ` TeusLollo
2023-10-07 9:40 ` SpidFightFR
2023-10-11 0:44 ` TeusLollo
2023-10-11 6:16 ` SpidFightFR
2023-10-11 6:22 ` SpidFightFR
2023-11-02 20:08 ` TeusLollo
2023-11-02 20:11 ` SpidFightFR
2023-11-02 20:16 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:54 ` TeusLollo
2023-11-02 21:26 ` TeusLollo
2023-12-07 3:40 ` ahesford [this message]
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=20231207034009.x8G9Hd08GWs5QnXRIG5hO9wgHAL7hEnUVs0icmAZiwI@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).