You are not logged in.
Okay, sorry, though in fairness I didn't even have any vague directions to look into. Thanks again!
Offline
Is it important that I'm using weston/sway? I've launched kwin on wayland and the leak became much worse. Just with Firefox running it already leaks 2.3 GB, 1.5 GB more than it would under X11.
I've checked that there's no X11 windows running.
Last edited by LaserMoai (2023-05-20 15:26:05)
Offline
Not unless this is a freak bug that's triggered by X11 and KWin…
We've ruled out the WM w/ openbox and so this would be to rule otu X11 (which doesn't seem to be the cause either)
Online
Stupid question: during the openbox test, was KDEs file indexer (baloo) running?
Can you try to disable it?
https://wiki.archlinux.org/title/Baloo# … he_indexer
If that thing leaks filehandles, it's probably gonna eat up RAM fast…
Online
No, it's definitely disabled. It tanks the performance with LUKS drives.
Offline
Hmm, the RAM leak metric is stably 600-800 megs if I only let the discrete GPU be used. I could've sworn that I've tested that option, I guess that was back when I wasn't properly measuring the leak size.
My laptop model is Lenovo Legion 5 15ACH6A, if that matters.
Offline
The natural contender would be gart/gtt then, but we tested that.
Can you also disable the GPU and only run on the AMD chip?
Online
I can't using the BIOS. I could try to blacklist it in the OS.
I have rechecked gart/gtt just in case.
Last edited by LaserMoai (2023-05-22 20:46:58)
Offline
I don't expect that to have significant impact, you're not reverse-priming, are you?
(Ie. run the software on the AMD GPU but have an output attached to the nvidia one)
Online
Both of the GPUs here are AMD. I'll probably figure this out tomorrow.
Offline
acpi_call hasn't managed to turn the GPU off at least. I can look for other options.
And no, I never use any outputs apart from the built-in screen.
Offline
https://wiki.archlinux.org/title/PCI_pa … _device_ID should hide the device from the OS
You previously disabled the IGP in teh BIOS/UEFI?
Online
I've managed to figure out how to isolate the GPU with vfio-pci, and the leak is still happening. Is this maybe some strange integrated GPU incompatibility?
Yeah, that was via UEFI.
Last edited by LaserMoai (2023-05-25 09:21:36)
Offline
Should I try the proprietary driver or something?
Offline
AMDGPU Pro is excusively a GL library; you can try that but I'd curb my expectations.
Online
It worked. Leak metric is stably 200-400 MB if I launch everything with progl in Openbox.
Last edited by LaserMoai (2023-05-26 20:03:36)
Offline
Filing a bug report to mesa is fair in this case, right?
EDIT: Never mind, I did it.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9107
Last edited by LaserMoai (2023-05-27 10:22:58)
Offline
The progl used does not come from upstream , but is a wrapper created by Ashark around the upstream one.l
It's listed on https://aur.archlinux.org/packages/amf-amdgpu-pro and the source is at https://raw.githubusercontent.com/Ashar … ster/progl
Knowing this detail may help mesa devs in figuring this out, please add it to the bug report .
Last edited by Lone_Wolf (2023-05-27 11:17:24)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
OK, done.
Offline