All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
To: Jellis Onsea | AccessWeb <jellis@accessweb.be>, zack.rusin@broadcom.com
Cc: dri-devel@lists.freedesktop.org, bcm-kernel-feedback-list@broadcom.com
Subject: Re: drm/vmwgfx: graphics memory not returned after all GEM objects are released
Date: Thu, 6 Aug 2026 14:24:50 -0700	[thread overview]
Message-ID: <5bbf4d74-d435-48d1-96ab-b119ce6fc4bc@broadcom.com> (raw)
In-Reply-To: <9a795e26-53de-41da-bdb8-9ced20b70e87@accessweb.be>

Hi,
As Zack mentioned, we have had issues with kwin attempting to gem_close() handles
causing a memory leak.
I have submitted a fix for it in mesa and it has been backported to 26.1 as well.
Could you please test things again with that fix?

To do so you can build the svga mesa driver (https://gitlab.freedesktop.org/mesa/mesa)
on either the main branch or staging/26.1 branch.
Alternately you can also wait for the release of the next release of mesa 26.1 which
would happen august 12th, or mesa 26.2 which should be our august 29th.

-- 
Maaz Mombasawala <maaz.mombasawala@broadcom.com>

  parent reply	other threads:[~2026-08-06 21:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 20:41 drm/vmwgfx: graphics memory not returned after all GEM objects are released Jellis Onsea | AccessWeb
2026-08-05 20:48 ` Zack Rusin
2026-08-06 21:24 ` Maaz Mombasawala [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-08 10:58 drm/vmwgfx: graphics memory not returned,after " Jellis Onsea | AccessWeb
2026-08-13 21:12 ` Maaz Mombasawala
2026-08-16 16:57   ` Jellis Onsea | AccessWeb
2026-08-17 22:02     ` Maaz Mombasawala
2026-08-18  1:08       ` Jellis Onsea | AccessWeb
2026-08-21  2:09         ` Maaz Mombasawala

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=5bbf4d74-d435-48d1-96ab-b119ce6fc4bc@broadcom.com \
    --to=maaz.mombasawala@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jellis@accessweb.be \
    --cc=zack.rusin@broadcom.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. 
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.