Bug 382602 - Video memory leak with desktop configured to slideshow
Summary: Video memory leak with desktop configured to slideshow
Status: RESOLVED DUPLICATE of bug 381000
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 5.10.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-22 19:08 UTC by Thomas Baag
Modified: 2017-07-23 15:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
GTT and VRAM usage shown by GALLIUM_HUD (9.07 KB, image/png)
2017-07-22 19:08 UTC, Thomas Baag
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Baag 2017-07-22 19:08:01 UTC
Created attachment 106788 [details]
GTT and VRAM usage shown by GALLIUM_HUD

VRAM and GTT usage steady increases when using desktop in wallpaper slideshow mode. It doesn't happen directly after starting plasmashell, but I can trigger it in under 60 seconds.

What I do:
1. Reset my plasma config
    mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~
2. Run plasmashell (in my case with GALLIUM_HUD to see VRAM and GTT info)
    GALLIUM_HUD="requested-VRAM,requested-GTT,VRAM-usage,GTT-usage" plasmashell
3. Set desktop to slideshow, configure a folder with tons of images and 
   keep change interval at 1 second.
(4. Bring up some other plasma surfaces which maybe triggers a race condition.)

What I see:
VRAM usage is increasing with every image up to a point where radeon driver says "no" with "radeon 0000:23:00.0: va above limit (0x00200407 >= 0x00200000)".

My system:
Linux stan 4.11.9-1-ARCH #1 SMP PREEMPT Wed Jul 5 18:23:08 CEST 2017 x86_64 GNU/Linux
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.5
Comment 1 Thomas Baag 2017-07-22 19:19:34 UTC
broulik.de
Comment 2 David Edmundson 2017-07-23 13:05:33 UTC
thanks, please follow linked report.

*** This bug has been marked as a duplicate of bug 381000 ***
Comment 3 Thomas Baag 2017-07-23 15:07:33 UTC
qt5-declarative package from Antonio Rojas linked in bug 381000 seems to have fixed the issue for me. Thanks a lot.