https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #134 from Evert Vorster <evors...@protonmail.com> --- (In reply to Nick H from comment #133) > Created attachment 181016 [details] > attachment-2251139-0.html > > Well spotted Evert. > > I thought I would give that a try too. In my case however with my ASUS TUF > A15 the option to only use the Discrete GPU is not available with > SuperGfxCtl, nor in BIOS, only the integrated option is available. My > system is a Prime set up that chooses the GPU automatically so perhaps that > may have something to do with it. > > While I'm typing, I'll mention I have just received the 6.14.5 kernel and > the memory leaks seem to be happening much much faster. Just a few minutes > and I can be at 80% used memory. 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 watching all bug changes.
