https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #138 from Nick H <kror...@gmail.com> --- Ahh that's interesting that we have two very similar setups (your wife's & mine) and potentially we could learn something here. I'm connected to a 2560x1440 AOC monitor via USB-c to display port cable, running at 144 hz, which is the same RR as my laptop screen. The laptop is 1080p 144hz but I keep it turned off via the OS. Ok so after writing that I decided to do some testing with my ext. monitor at 1080p@60hz. An hour on Cyberpunk 2077 and then Kwin was using only 490mb. Impressive. I thought it was fixed. I tried some CS2, but from there Kwin jumped up 1 and then 2gb. I played another low system requirements game that added more. Then I did some quick gaming at 1440p@144hz and kwins usage increased much quicker. I concluded that running at 1080p@60hz does not fix the problem but does reduce (or turn the tap down on) the memory leaking significantly. On Thu, 8 May 2025, 02:59 Evert Vorster, > Hi Nick. > I checked online, and your laptop does not have a MUX switch, so the > option to > just use the dGPU for everything is not available. > This is because the dGPU is simply not wired to any output. > > My wife's laptop, a very similar Asus TUF A15 with a slightly different > AMD cpu > also does not have the mux switch. > What are the chances? > > It is also running Arch linux, and just been updated. It is running in > Hybrid > mode, and I can confirm that only Integrated and Hybrid modes are > available in > supergfxctl. > > What is very interesting is that there does not appear to be a memory leak > in > kwin_wayland on that laptop. I've been watching it for a while, and can > confirm > that kwin_wayland's memory consumption is sitting dead still at 330Mb. > That laptop is connected to an external screen as well, but only 1080p at > 60Hz > refresh rate. > > How are you driving your external monitor, what resolutions and refresh > rates > are you using? > I have a hunch that this might be related to the resolution/refresh rates > that > some higher end external monitors are capable of. I don't know much about > programming, but this might just be a buffer that is sufficient for lower > resolutions and then blows up when you really push it. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
