Bug 371559 - After a half-day starts slow, freezing and consume CPU
Summary: After a half-day starts slow, freezing and consume CPU
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-24 09:18 UTC by Alexey
Modified: 2018-10-27 04:06 UTC (History)
2 users (show)

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


Attachments
atop avg (326.57 KB, image/png)
2016-10-25 07:14 UTC, Alexey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey 2016-10-24 09:18:46 UTC
In the evening (after a work day) lock the screen, the morning after unlocking the system slows down, there are delays on all the action, the movement of the mouse cursor intermittent. Reboot solves the problem to the next iteration.


Reproducible: Always

Steps to Reproduce:
1. Work
2. Lock the screen on a most time
3. Watch




I straced plasmashell process.
When system slowdown:
poll([{fd=3, events=POLLIN}], 1, -1)    = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="g\0\352 3\0\300\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 4096
futex(0x20367e4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20367e0, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20367b8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}], 1, -1)    = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="g\0\352 3\0\300\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 4096
futex(0x20367e4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x20367e0, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x20367b8, FUTEX_WAKE_PRIVATE, 1) = 1
...
repeatly
Comment 1 David Edmundson 2016-10-24 09:39:27 UTC
So is the lock screen process taking up a lot of CPU? Is anything else?
Is there some intense disk activity? Does this happen if you don't lock the screen?
Comment 2 Alexey 2016-10-24 09:55:42 UTC
In my case, consumes CPU the plasmashell process ("plasmashell --shut-up"). Without blocking the screen I did not try - check today.
No other anomalies no disk activity\network activity there. Plasmasnell process consumes about 25% of cpu (I suspect one CPU core).
If a short time to lock screen, then no problem. The problems begin after a long inactivity (such as after a night).
Comment 3 Alexey 2016-10-25 07:14:47 UTC
Created attachment 101766 [details]
atop avg

The picture shows the state of the system.
Comment 4 Alexey 2016-10-25 07:21:52 UTC
I turn off screen lockscreen, and start atop daemon at night. The situation does not change, already at the end of the day the plasma begins to consume the processor. At night, load average about 1.0-1.5,  plasma and xorg have CPU consumption,. I can attach a dump of atop, but it has a big size (about 250M). I have CPU consumation and freezes right now, we can debug it.
Comment 5 Alexey 2016-11-08 06:57:12 UTC
I update to 5.8.3 . Problem still there
Comment 6 Andrew Crouthamel 2018-09-26 22:20:22 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: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status 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 7 Andrew Crouthamel 2018-10-27 04:06:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!