Bug 447952 - [NVIDIA] Plasmashell eating up memory when screen locked with automatic/OpenGL rendering backend; fixed with software rendering backend
Summary: [NVIDIA] Plasmashell eating up memory when screen locked with automatic/OpenG...
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (show other bugs)
Version: 5.23.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
Depends on:
Reported: 2022-01-04 23:52 UTC by Andy
Modified: 2022-02-25 04:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Output of journalctl with grep for kernel and plasmashell (24.49 KB, text/x-log)
2022-01-04 23:52 UTC, Andy
Valgrind output (3.82 MB, application/gzip)
2022-01-04 23:55 UTC, Andy

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2022-01-04 23:52:45 UTC
Created attachment 145119 [details]
Output of journalctl with grep for kernel and plasmashell

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.

1. Set rendering backend to automatic (default)
2. Lock screen
3. Wait

Eventually plasma will use up too much memory and the kernel will kill it.

Plasma not using up memory

Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

Kernel 5.15.12-1 Manjaro
NVidia driver version: 495.44
Comment 1 Andy 2022-01-04 23:55:56 UTC
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
Comment 2 Nate Graham 2022-01-12 20:20:21 UTC
What's your lock screen background? A still image, a slideshow, or something else? And what Plasma theme are you using?
Comment 3 Andy 2022-01-13 08:38:31 UTC
I am using "Breath Dark" as a theme. The lock screen is just the default  image that comes with Manjaro. No slide show.
Comment 4 Nate Graham 2022-01-13 18:10:23 UTC
Does it still happen if you switch to the Breeze Plasma theme?
Comment 5 Andy 2022-01-14 15:24:43 UTC
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.
Comment 6 Nate Graham 2022-01-14 16:24:38 UTC

What GPU hardware do you have?
Comment 7 Andy 2022-01-15 00:40:48 UTC
I am running a NVIDIA GeForce GTX 1060
Comment 8 Bug Janitor Service 2022-01-30 04:37:14 UTC
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:

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!
Comment 9 Andy 2022-01-30 19:33:35 UTC
I did reply with the card I have. What else is missing?
Comment 10 Nate Graham 2022-01-31 18:01:19 UTC
Thanks for the info.
Comment 11 David Edmundson 2022-02-23 23:38:02 UTC
Could you run with heaptrack rather than valgrind.
Comment 12 Andy 2022-02-25 04:28:12 UTC
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.