https://bugs.kde.org/show_bug.cgi?id=368838
Alexander Schlarb <alexander-kde@ninetailed.ninja> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexander-...@ninetailed.ni
| |nja
--- Comment #48 from Alexander Schlarb <alexander-kde@ninetailed.ninja> ---
Moving discussion here from my bug report at 388580…
Summary of my findings form that other thread (Radeon R9 M280X, Linux 5.9 –
5.15, Mesa any version, Qt 5.9.3):
1. The issue doesn't occur with the "AMD GPU Pro" userland GL stack (in
return you get s***loads of other issues) – only MESA (including ancient
versions) is affected
2. Memory usage of the offending process will be accounted correctly with
running it with `LIBGL_ALWAYS_SOFTWARE=true`, but the leaking issue will
persist
3. The leak can be greatly accelerated by enabling the "Media-Frame" Plasmoid
4. I am absolutely not able to compile a working Qt + KDE stack to bisect
this issue
5. (Setting `QSL_RENDER_LOOP=threaded` seems to make the issue go away ←
Still investigating this currently!)
@Matt Whitlock
> Have you tried running radeontop?
`radeontop` doesn't work on my system (Debian unstable with current 4.15.0
kernel):
amdgpu DRM driver is used, but amdgpu VRAM size reporting is not enabled
amdgpu DRM driver is used, but amdgpu VRAM usage reporting is not enabled
Failed to get VRAM usage, kernel likely too old
Do you think there are any insights to be gained by compiling a custom kernel
for this?
One other thing I noticed (not sure if its related to this issue) is that when
enabling DisplayCore (DC) for the `amdgpu` driver (kernel flag `amdgpu.dc=1`),
I get lots of these messages in `dmesg`:
swiotlb: coherent allocation failed for device 0000:00:01.0 size=2097152
CPU: 0 PID: 9635 Comm: kworker/u8:15 Tainted: G O
4.15.0-1-amd64 #1 Debian 4.15.4-1
Hardware name: LENOVO 80NY/Allsparks 5B, BIOS CECN43WW 09/15/2015
+ A long stack trace with calls such as: `amdgpu_gem_object_create`,
`ttm_tt_bind` and `swiotlb_alloc_coherent` (i.e.: memory related)
This may be related to the accounting issues…
--
You are receiving this mail because:
You are watching all bug changes.
