https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #133 from Nick H <kror...@gmail.com> --- 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. On Mon, May 5, 2025 at 11:35 AM Evert Vorster <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=496469 > > --- Comment #132 from Evert Vorster <evors...@protonmail.com> --- > Can confirm that when the system is in dGPU only mode, this issue is gone. > > My system supports three different graphics modes, Integrated, Hybrid and > AsusMuxDgpu. > > With Integrated mode, the nVidia card is switched off, and so the external > monitor does not work. > In Hybrid mode, the dGPU drives the external monitor through the HDMI port > and > the iGPU drives the internal monitor. The dGPU also does render offloading > to > the laptop's panel if needed. > So, when I plug in the external monitor, the dGPU fires up anyways, and no > power saving benefits are to be had there. > > On the last mode, the nVidia dGPU drives both the monitors and does the > compositing too. The AMD GPU sits mostly idle. > > Since this issue only pops up when the external monitor is connected in > Hybrid > mode, and the dGPU fires up in any case to drive the external monitor, > AsusMuxDgpu mode is an acceptable workaround for me while the external > monitor > is connected. > It is easy enough to switch with supergfxctl, an no fannying around in the > BIOS > is needed, just a set and reboot command. > > -- > 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.
