More data:

Now from `vmwgfx_gem_info` (3h uptime, KDE Wayland, three 1920x1080
outputs):

    kwin_wayland   18.5 GB   4054 objects   2068 of them >= 1920x1080x4
    plasmashell     1.0 GB   3383 objects    105
    Xwayland         33 MB      18 objects      3

kwin's GEM total and GPUActive rise together (+0.13 vs +0.10 GB over the same 5 min), and 570 of its objects are down to a single GEM ref. Growth is bursty and tracks render activity, not uptime.

Your patch did fix its own target: zero gem_close errors this boot.

One thing that may be worth a look: mesa 26.2.1 (libgallium) logs

    Failed referencing shared surface. SID <n>
    Error -22

572 times this boot, across 123 distinct surface IDs, 402 of them in the hour with five RDP sessions open. I can't tell you whether that is new the pre-patch boot had too little comparable activity to compare against.

Op 27-08-2026 om 15:39 schreef Jellis Onsea | AccessWeb:
Tried the scanout patch on kernel 7.2.0. Confirmed running:
`[drm] Initialized vmwgfx 2.22.0`.

No change here. GPUActive from /proc/meminfo:

     5 RDP sessions, 39 min open:   0.70 -> 3.97 GB
     then 42 min at zero sessions:  3.92 -> 4.73 GB

Not a single sample went down. Same as on 2.21.

It also keeps growing with zero sessions and small usage of the machine, so RDP is a good trigger, not the only one.

Build details if useful: distribution kernel (CachyOS 7.2.0-1), vmwgfx built out-of-tree from the matching source with clang 22.1.8, no LTO.


Regards,

Jellis

Op 27-08-2026 om 03:01 schreef Maaz Mombasawala:
On 8/26/26 7:17 AM, Jellis Onsea | AccessWeb wrote:
Hi Maaz,

Short version: mesa 26.2.1 is running here with 3D on, and the leak is still there.

Setup: one boot, 119 h, a single kwin_wayland (6.7.4), mesa 3:26.2.1-1, kernel 7.2.0, renderer SVGA3D.

   TTM sys+mob    0.36 -> 16.73 GB
   objects        1948 -> 10365
   kwin_wayland   holds 8484 MB in 4894 objects
   free RAM       4.9 of 31 GB - we have to reboot today

It tracks rendering, not uptime. Idle nights (02:00-07:00) in this same boot:

   22 Aug  -0.03 GB       25 Aug  +0.00 GB
   23 Aug  +0.02 GB       26 Aug  +0.04 GB
   24 Aug  +1.88 GB   <- the one night an automated GUI test run was active

The surface warning still fires: 1168 WARNING blocks at vmw_surface_handle_reference in the last 27 hours. That is a window, not a total - journald has already rotated away the earlier part of this boot.

Correction to my previous mail: "four times during session startup" was wrong. It fires in bursts throughout the session.

We have not tried "drm/vmwgfx: Return gem fd handle for scanout buffers" we run distribution kernels here. Say the word and we will build it.
Yes please, can you go ahead and try that patch, it fixes some errors on kde and might fix this issue you are facing too.

Best regards,
Jellis

Op 21-08-2026 om 04:09 schreef Maaz Mombasawala:
For the 3D-enabled case, could you try with mesa 26.1.8 or 26.2.1, both of which contain my fix. Also if you could try the patch I just submitted on dri-devel - drm/ vmwgfx: Return gem fd handle for scanout buffers.
If you still see issues with these patches, let me know.

As for the 3D disabled case, I can see issues on my local machine and am working on a fix.

PS - Your emails are overly verbose and narrative, could you include only the actual problems you are facing. If you're using an llm to write these, please make them more terse and human readable. Thanks.








Reply via email to