Bug 365599 - high cpu usage of plasmashell when rsibreak is running
Summary: high cpu usage of plasmashell when rsibreak is running
Status: RESOLVED WORKSFORME
Alias: None
Product: rsibreak
Classification: Applications
Component: general (other bugs)
Version First Reported In: 0.12
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-07-13 09:05 UTC by coder53
Modified: 2018-10-27 02:38 UTC (History)
1 user (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 coder53 2016-07-13 09:05:34 UTC
When rsibreak is not running (or be suspended), plasmashell use 1-5%CPU
Start rsibreak, plasmashell use 20-25%CPU
It seems related to system tray applet

Reproducible: Always
Comment 1 Albert Astals Cid 2016-07-13 22:02:38 UTC
Which rsibreak and plasma versions are you using?
Comment 2 coder53 2016-07-14 02:11:40 UTC
I'm using:
rsibreak 0.12
plasma 5.7.1
Comment 3 Albert Astals Cid 2016-07-14 21:46:51 UTC
Do you remember if this was happening with older plasma versions or you just installed rsibreak?
Comment 4 coder53 2016-07-15 02:01:31 UTC
I have been used rsibreak for a long time and yes, it happening for older plasma versions, at least since 5.6
Comment 5 Albert Astals Cid 2016-07-19 21:22:18 UTC
I can't reproduce it here with plasma 5.7 on arch, can you send your .config/rsibreakrc over in case it's something in your local configuration?
Comment 6 coder53 2016-07-20 02:36:59 UTC
OK, i just figure out that change config to 'break in a fixed time' is reason for this issue.
Comment 7 Albert Astals Cid 2016-07-21 20:27:35 UTC
Do you mean that changing the setting to "Take into account activity" makes the CPU usage go away?
Comment 8 coder53 2016-07-22 02:16:07 UTC
Not really. I try debug using strace command and find out high cpu usage of plasamashell is because this systemcall:
sendmsg(11, {msg_name(0)=NULL, msg_iov(2)=[{"l\4\1\1\0\0\0\0\32\0\0\0[\0\0\0\1\1o\0\23\0\0\0/StatusNotifierItem\0\0\0\0\0\2\1s\0\32\0\0\0org.kde.StatusNotifierItem\0\0\0\0\0\0\3\1s\0\n\0\0\0NewT"..., 112}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 112

If setting is 'Take into account activity': rsibreak only sends msg to kde notifier if user has an activity (using mouse, keyboard,...)
if setting is 'break in a fixed time' rsibreak send msg to kde notifier every 1 second.
So if I change setting to 'Take into account activity' will not really make the high CPU usage go away.
Comment 9 Albert Astals Cid 2016-07-24 21:54:59 UTC
Sorry but i do not really understand your messages, it seems to me you're saying one thing and then in the next sentence a different thing.

Could you attach the rsibreakrc that makes you have high cpu usage to see if i can reproduce it?
Comment 10 coder53 2016-07-25 02:11:52 UTC
 This is my rsibreakrc:

[General]
AutoStart=false
LastRunBigLeft=3586
LastRunTimeStamp=2016,7,25,9,7,43
LastRunTinyLeft=1786

[General Settings]
BigDuration=1
BigInterval=60
DisableAccel=false
Effect=0
Graylevel=80
HideLockButton=false
HideMinimizeButton=false
HidePostponeButton=false
ImageFolder=/home/thinhnt
Patience=30
PostponeBreakDuration=5
SearchRecursiveCheck=false
ShowSmallImagesCheck=true
SlideInterval=10
TinyDuration=20
TinyInterval=10
UseNoIdleTimer=true
UsePlasmaReadOnly=true

[Notification Messages]
dont_show_welcome_again_for_001=false

[Popup Settings]
UseFlash=true
UsePopup=true
Comment 11 Albert Astals Cid 2016-08-01 21:50:36 UTC
I've run with that configuration both in Plasma 5.5.5 and Plasma 5.7.2 and can not reproduce the high cpu usage.

At this point i don't know what to try, sorry :/
Comment 12 coder53 2016-08-04 17:30:36 UTC
High CPU usage of plasmashell only happen when has another app's icon on system tray (eg: goldendict, amarok, clementine,...)
Reproduce successfully on live KDE Neon image (Plasma 5.7.2)
Comment 13 Andrew Crouthamel 2018-09-26 22:09:41 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 14 Andrew Crouthamel 2018-10-27 02:38:12 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!