Kwin_wayland vram use, windows not updating compositor?

Help
, ,
1

I’ve been trying to use wayland, and since I found dynamic wallpapers caused my worst memory leak in 2 decades, KDE 6 is finally somewhat usable in Wayland.

Lately my worst issue is the compositor seems to weird out not refreshing windows, and kwin_wayland will collect like ~3.4gb of vram usage, which with everything else in kwin and other desktop usage affects my gaming and trying to use ollama (and my laptop has a 3080rtx with 16gb). Is that really normal or not using 3x4k displays normallly, and sometimes 4, but it seems to eventually drive KDE and kwin mad? Plasmashell otherwise stays around 600mb vram, but while kwin_wayland starts that too, it grows to 3.4gb over time or as my current system is after uptime of 35 days.

I have for a while noticed windows will stop updating, like I’ll see in kde plasma task manager an active signal window, click on it, and it doesn’t show refreshed, and clicking about I notice even not users are updating as I click between them. It’s not a new thing, but I suspect I push it more than most with 3-4x 4k displays and nvidia drivers. I minimize and refresh, and I’ll see it updated now. Weird, and it’s not only signal, but firefox/librewolf I notice most not updating to have to force a compositor update to the window, or I assume.

I suspect it’s probably the the usual devil, nvidia, doing it, but I really can’t tell other than wayland freaking out and using all my vram on gpu per nvtop. I’ve seen before this seems abnormal for usage, so what is gobbling all my vram with kde+wayland+nvidia? Will a heaptrack show this to anyone to fix? Does anyone see this with amd?

This is NOT new, what is new is me not having to restart every few weeks for above the wallpaper bug forcing me, but now these refresh issues with what I suspect is kwin compositing being cranky (after some 15+ years of watching the like).

Most notably I find lately signal, firefox/librewolf, even steam will do it, so I suspect some compat layer, but not sure.

Any thoughts how to help fix this? I swear even in its most stable it’s done this since 5.x with kwin compositing, but finally this is the least annoying to troubleshoot.

2

Also, just a thought - it doesn’t do this after a fresh boot, it’s after a while, after several weeks, like a memory leak it degrades…

3

Oh, signal == electron, and I get this lately with the electron slack client too, I at times have to restart it to get updates to the window itself for a customer of mine.

This seems like a legacy vs wayland vs nvidia issue, but who knows. I do know this same thing has happened with KDE+X/Wayland+Nvidia as long as I can imagine from almost 4.x days to some respect, there is a very fundamental problem with whatever kde/kwin tracks with the gpu for this.