Created attachment 117512 [details] Video showing difference between opening with systemsettings5 and standalone SUMMARY When I try to set a wallpaper for the lock-screen, if I access the screenlocker module from system settings I can choose an image normally, but if I start the screenlocker module "standalone" (eg. from the command line or from krunner) and select the "Aspect" tab when I try to resize it or scroll it, it shows severe ""redrawing"" problems. STEPS TO REPRODUCE 1. Open terminal and execute "kcmshell5 screenlocker" 2. Select "Aspect" tab 3. Try to resize the window or scroll through the images OBSERVED RESULT The screenlocker window doesn't redraw itself like it does when accessed from the system settings. EXPECTED RESULT The screenlocker module opened standalone should redraw itself as good as it does when opened from system settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: Plasma 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I am appending a video showing the described issue (note: the window gets updated eventually, it was just taking too long so I cut the video)
Created attachment 117513 [details] qdbus org.kde.KWin /KWin supportInformation
Forgot to add that I am using software plasma renderer.
1. Is it just the screenlocker KCM that exhibits this problem, or other KCMs too? 2. Do you see the problem if you use Sidebar view instead of icons view for the System Settings app itself?
(In reply to Nate Graham from comment #3) > 1. Is it just the screenlocker KCM that exhibits this problem, or other KCMs > too? > 2. Do you see the problem if you use Sidebar view instead of icons view for > the System Settings app itself? 1. Looking through other KCMs I can effectively confirm that at least "Look and Feel","Desktop Theme", "Cursor Theme", "Splash Screen" (all accessible from "Workspace Theme" inside system settings) and "Icons" are also affected by the same problem. 2. I do not see the problem using sidebar or tree view for the system settings.
Strange!
I discovered something. When I resize the kcm modules from system settings (so the one that is currently redrawing the window with good responsiveness), there is a big memory leak. When I open System Settings and go to the "Workspace Theme" section (therefore I opened one of the problematic kcm modules), it occupies 47MB of ram. Then I start to resize the window continuously for 5 seconds: the systemsettings5 process now occupies 375MB of ram. It basically sky rockets the more I keep resizing. This fast leak happens on the kcm modules aforementioned. This does NOT happen when I open the kcm modules standalone (in that case it's the cpu going to 50% usage -> so 1 core to 100%, since I got 2). Although the leak I described above is by far the most aggressive, I noted that if I try to keep resizing other non affected kcm modules (both from system settings and standalone mode), or a newly opened system settings window, I still see a ram leak: a newly opened system settings window occupies around 28MB of ram, if I keep resizing it for 5 seconds it gets to 52MB of ram.
Git commit e8fe68581741f375c1b1d73e10c42bf41e4c2f9a by David Edmundson. Committed on 22/01/2019 at 12:39. Pushed by davidedmundson into branch 'Plasma/5.15'. Load Plasma QtQuick settings in KCMShell Summary: FIXED-IN: 5.15.0 Test Plan: Clone of code used in systemsettings etc. Compiles Reviewers: #plasma, broulik Reviewed By: #plasma, broulik Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D18443 M +1 -0 CMakeLists.txt M +1 -0 kcmshell/CMakeLists.txt M +2 -0 kcmshell/main.cpp https://commits.kde.org/kde-cli-tools/e8fe68581741f375c1b1d73e10c42bf41e4c2f9a