Created attachment 145119 [details] Output of journalctl with grep for kernel and plasmashell SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Whenever I lock my screen plamsashell starts to use more and more memory until it gets killed by the kernel. This doesn't happen if I switch the rendering backend from automatic to software. I did run valgrind to see if it logs anything, but unfortunately it didn't. STEPS TO REPRODUCE 1. Set rendering backend to automatic (default) 2. Lock screen 3. Wait OBSERVED RESULT Eventually plasma will use up too much memory and the kernel will kill it. EXPECTED RESULT Plasma not using up memory SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel 5.15.12-1 Manjaro NVidia driver version: 495.44
Created attachment 145120 [details] Valgrind output Executed with: valgrind --leak-check=full --show-reachable=yes --track-origins=yes --trace-children=yes --log-file=plasmashell.log plasmashell
What's your lock screen background? A still image, a slideshow, or something else? And what Plasma theme are you using?
I am using "Breath Dark" as a theme. The lock screen is just the default image that comes with Manjaro. No slide show.
Does it still happen if you switch to the Breeze Plasma theme?
Switched to the Breeze theme and turned the rendering backend back (kcmshell5 qtquicksettings) to automatic. When I unlocked this morning plasmashell got killed again. As I said, it only happens when the backend is set to the default automatic. It doesn't happen when it is set to software.
Thanks. What GPU hardware do you have?
I am running a NVIDIA GeForce GTX 1060
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I did reply with the card I have. What else is missing?
Thanks for the info.
Could you run with heaptrack rather than valgrind.
I am running 5.23.5 by now, plus other upates. I tried to reproduce the issue and it seems it is not happening anymore. I switched the backend back to automatic and it doesn't eat up my memory. Now it seems to eat up a CPU. Either way I would say this issue can be closed. It seems to be fixed. I will try to figure out why it eats a CPU now. Thanks!