> But then this sounds like a bug in that particular compositor rather than the driver(s)?

The NVIDIA GPU memory allocation issue affects all NVIDIA cards, at least based on that forum post where there's a good amount of people replying with similar issues with a large combo of cards + drivers.

You probably don't notice it because you rarely ever use all of your GPU's memory at once. Try running `watch nvidia-smi` and then open multiple copies of every hardware accelerated app you have available. Once you reach nearly the max GPU memory apps will either start crashing or fail to open and if you get semi-unlucky your compositor (including KDE on Wayland) will crash if it's the app trying to allocate resources to render the window. I've had plasmashell or kwin hard lock / crash many times with just a small amount of testing.

The expectation is the driver allocates those memory resources to system memory instead of denying the memory to the app. It works correctly in X11 or if you have an AMD card, in Wayland and X11.

The leak is separate and is compositor specific, possibly related to NVIDIA driver bugs (to some degree) but this leak wouldn't be experienced unless you used this compositor. This leak is the compositor doesn't release any GPU memory after any window is closed, so simply opening and closing apps will cause the leak. Combine this with the first problem and that's how you end up rebooting every few hours with a lower end GPU. AMD and NVIDIA are affected.

The post goes into all of these details and there's reproducible tests, and even demo videos showing the first GPU memory allocation problem in Plasma Wayland but not Plasma X11. It also links to all of the related GitHub issues that I could find.