all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ott Joon via <help-guix@gnu.org>
To: Robby Zambito <contact@robbyzambito.me>
Cc: Guillaume Le Vaillant <glv@posteo.net>, Help Guix <help-guix@gnu.org>
Subject: Re: OBS Studio memory leak
Date: Tue, 13 Jun 2023 16:03:40 +0200 (CEST)	[thread overview]
Message-ID: <NXp3R72--Z-9@tutanota.com> (raw)
In-Reply-To: <87v8frms26.fsf@robbyzambito.me>

Awesome! Worked for me, too! 
Also fixed the issue with the gst-plugin-helper memory leak. 
So it must have all been to do something with the mesa shader cache. 
VLC seems to struggle playing an HEVC encoded 2K video however while mpv does it just fine. 
virt-manager is running smoothly again.


13. juuni 2023 16:04 poolt contact@robbyzambito.me:

>
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> It looks like an issue with the shader cache of mesa.
>> After clearing it, I don't see the memory leak anymore.
>>
>> Could you try doing a "rm -r $HOME/.cache/mesa_shader_cache/*" and see
>> if it also solves the issue for you?
>>
>
> This worked for me! Thank you!
>



  reply	other threads:[~2023-06-14  5:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NXj2j6I--3-9@tutanota.com>
2023-06-12 12:49 ` OBS Studio memory leak Robby Zambito
2023-06-13  7:31   ` Guillaume Le Vaillant
2023-06-13  8:05     ` Ott Joon via
2023-06-13 12:41       ` Robby Zambito
2023-06-13 12:41       ` Guillaume Le Vaillant
2023-06-13 13:04         ` Robby Zambito
2023-06-13 14:03           ` Ott Joon via [this message]
2023-07-22  4:58           ` Dr. Arne Babenhauserheide
2023-06-15 10:26         ` stateful caches (was Re: OBS Studio memory leak) Giovanni Biscuolo
2023-06-15 11:41           ` Guillaume Le Vaillant
2023-06-15 12:59             ` Giovanni Biscuolo
2023-06-10  0:09 OBS Studio memory leak Robby Zambito

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=NXp3R72--Z-9@tutanota.com \
    --to=help-guix@gnu.org \
    --cc=contact@robbyzambito.me \
    --cc=glv@posteo.net \
    --cc=ott.joon@tutanota.com \
    /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.