Bug 1437843

Summary: Datetime plugin eats CPU when showing calendar
Product: [Fedora] Fedora Reporter: Zdenek Kabelac <zkabelac>
Component: xfce4-datetime-pluginAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: nonamedotc, rosset.filipe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 17:38:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zdenek Kabelac 2017-03-31 09:59:04 UTC
Description of problem:

When datetime plugin is showing calendar - it eats 10% of  2GHz CPU.

I've absolutely no idea what is this plugin doing internally,
but externally on my display nothing.

'perf record' tells me something about higher usage of:

gtk_css_selector_tree_get_change
gtk_css_selector_tree_collect_change
and couple other functions....

So it looks like calendar is being endlessly refreshing screen???


Feel free to make it upstream BZ..

Version-Release number of selected component (if applicable):
xfce4-datetime-plugin-0.7.0-2.fc26.x86_64

How reproducible:


Steps to Reproduce:
1. click on time in panel
2. see 'calendar' and CPU being eaten

Actual results:


Expected results:
CPU is idle when calendar is 'shown'

Additional info:

Comment 1 Zdenek Kabelac 2017-06-26 18:31:51 UTC
I've changed  to  'Clock'  plugin.

Looks very similar, but doesn't have the issue of 'datetime-plugin'

So I'm mostly no longer watching what's doing the other one....

Comment 2 Jan Kurik 2017-08-15 06:53:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 3 Ben Cotton 2018-11-27 18:38:36 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2018-11-30 17:38:35 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.