SUMMARY "plasmashell" is froze and began 100% 1 core cpu usage and unlimited memory consumption when opening the "Notifications" applet. STEPS TO REPRODUCE 1. A notification came to my computer via "KDE Connect" from my smartphone 2. I clicked on the "Notifications" button (Bell icon) in the system tray OBSERVED RESULT ... and at this moment all the plasma elements (taskbar, system tray, application menu, clock) froze and did not react to any actions. The "Notifications" window did not appear. In the system monitor, I found that the "plasmashell" process began to load 1 CPU core by 100% and a large consumption of RAM and swap (memory leak). EXPECTED RESULT Displaying the "Notifications" applet. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.10.84-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® Silver N5000 CPU @ 1.10GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 605 ADDITIONAL INFORMATION I brought up a terminal and entered the command "killall plasmashell && kstart5 plasmashell". Then the plasma shell rebooted, CPU loading and RAM consumption stopped and all plasma elements began to function normally.
Noticed the same as well. Don't even have to open Notifications applet, just wake the system from Sleep. Plasmashell starts using 100% of one CPU core, and memory usage creeps up a bit. Killing and restarting Plasmashell fixes the problem until the next time the computer wakes from Sleep. My platform is very similar, except Frameworks is 5.89.0, Kernel is 5.14.21-2-MANJARO, and CPU is a 4-core i5-3320M @ 2.6 Ghz
Happened again, seemingly on random. I'll perhaps do some more testing to see what triggers it. Maybe even post logs.
Thank you for reporting this issue in KDE software. As it has been a while since it was reported, can we please ask you to see if you can reproduce the issue with a recent software version? Like Plasma 5.25, or ideally 5.26? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
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!
(In reply to Nate Graham from comment #3) > Thank you for reporting this issue in KDE software. As it has been a while > since it was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? Like Plasma 5.25, or ideally 5.26? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Hello dear Nate Graham. I tried to reproduce the problem in KDE Plasma versions 5.23.4, 5.23.5, 5.24.4, 5.26.3, but the problem never showed up. Perhaps this problem is related to something else, it just manifested itself at the time of interaction with the Notifications applet. This has happened before while working in different applications (more often when working in the Firefox browser). Thank you!
Ok, that's good to hear. Unfortunately for this bug report, if nobody can reproduce it, it isn't really actionable. Closing.