Bug 444034 - Plasmashell semi-freeze after and display bugs after a few hours or after sleep/hibernate
Summary: Plasmashell semi-freeze after and display bugs after a few hours or after sle...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (show other bugs)
Version: 5.21.5
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-19 11:30 UTC by Nataniel
Modified: 2024-09-17 03:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nataniel 2021-10-19 11:30:50 UTC
SUMMARY
Since a few weeks, after a few hours of uptime, krunner, my applets (application launcher, notes, folder view, calendar... anything that is on my panels) become super un-responsive, taking between 5 and 10 seconds to answer. Additionaly, my panels resize themselves randomly (I'm using a Unity-like layout, with 2 plasma-panels left and top).

STEPS TO REPRODUCE
1. Boot, log-in, use the computer for internet browsing, music-listening, emails, libre-office. Sometimes Inkscape, QGIS and Tracktion Waveform (non-free DAW). Do this for 1 hour or more.
1 (alternate). Boot, etc. and sleep or hibernate.
2. Invoke an applet on the panels: clicking on the application launcher or hitting "super" key, clicking on some applets on the panels (show desktop, present-windows applet and simple pager applet are NOT affected by this)


OBSERVED RESULT
The invoked applet immediatly appears, but is unresponsive for a few seconds. Clicking on the desktop or an app to make it disappear doesn't work instantly either. The applet then eventually responds. 
Searching krunner or the app launcher takes even more time. As I type, letters do not appear instantly but also take seconds, then once the text appears it takes another 10 seconds to display results. Clicking on a result instantly launches apps. Apps themselves are not affected at all.

Clicking on folder view, date and time, quick notes and system tray behaves similarly slow.

Sometimes, the panels resize a bit, not touching each other anymore.

A reboot solves all of this. As well as 'kquitapp5 plasmashell && kstart5 plasmashell' command.

EXPECTED RESULT
Plasmashell and its components are responsive at boot but also later on.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.10.70-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3840QM CPU @ 2.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Comment 1 Nate Graham 2021-10-20 13:39:52 UTC
Is anything using up a lot of CPU or memory resources when this happens?
Comment 2 Nataniel 2021-10-21 13:05:40 UTC
(In reply to Nate Graham from comment #1)
> Is anything using up a lot of CPU or memory resources when this happens?

Not really, nothing interesting in System Monitor, be it CPU (rarely above 30%) or RAM...
Comment 3 Nate Graham 2021-10-21 15:19:38 UTC
Thanks.
Comment 4 Nataniel 2021-10-25 15:13:38 UTC
(In reply to Nataniel from comment #2)
> (In reply to Nate Graham from comment #1)
> > Is anything using up a lot of CPU or memory resources when this happens?
> 
> Not really, nothing interesting in System Monitor, be it CPU (rarely above
> 30%) or RAM...

upon closer look, the CPU is slightly more used, ranging between 15-30% vs 2-15% after I run 'kquitapp5 plasmashell && kstart5 plasmashell' command
Comment 5 Philipp Keck 2023-02-19 12:24:31 UTC
Same here regarding sluggishness/unresponsiveness after hibernate, actually for 10-30s. And even after that is over, sometimes it works again and other times it's just as sluggish when I try to use it again a few seconds later -- until I kquit&&kstart.
Though I haven't observed the random panel resizing.

Operating System: Linux Mint 21.1
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-58-lowlatency (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6400 CPU @ 2.70GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 745/PCIe/SSE2

In https://bugs.kde.org/show_bug.cgi?id=451840, someone reported similar symptoms, though under Wayland (not X11 like here) and after suspend only, not hibernate (unlike here). Still I wonder if the clipboard history could be at fault somehow, perhaps an equivalent fix for X11 is needed as the one they did for Wayland in https://bugs.kde.org/show_bug.cgi?id=454379.

I'll try to look for high CPU/RAM usage the next time.
Comment 6 Alexander 2024-03-17 13:49:36 UTC
I have the same issue - almost every time after sleeping plasmashell uses ~60% RAM, so I need to kill and restart it. Sometimes I need to restart Chrome after that too. No high CPU usage detected.

Operating System: Kubuntu 22.04.4 LTS
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-100-generic
Graphics Platform: X11
Processors: 4 × Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
Memory: 8.7 GiB of RAM
Graphics Processor: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)
Comment 7 Nate Graham 2024-08-18 22:36:49 UTC
Unfortunately each of these issues is likely different, with a different root cause. Nataniel, are you still able to reproduce the issue in Plasma 6.1.4 or later?
Comment 8 Bug Janitor Service 2024-09-02 03:47:13 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2024-09-17 03:47:10 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.