Bug 1166838 - Graphs in resource tab of gnome-system-monitor are delayed
Summary: Graphs in resource tab of gnome-system-monitor are delayed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-21 16:57 UTC by czerny.jakub
Modified: 2015-12-02 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 05:09:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
load not yet drawn (45.29 KB, image/png)
2014-11-21 16:57 UTC, czerny.jakub
no flags Details
no load not yet drawn (44.97 KB, image/png)
2014-11-21 17:00 UTC, czerny.jakub
no flags Details

Description czerny.jakub 2014-11-21 16:57:03 UTC
Created attachment 959870 [details]
load not yet drawn

Description of problem:
Graphs depicting history of measured quantities (CPU, Memory & swap, Network) in Resources tabs are delayed with respect to both reality and counters shown below these graphs. The delay is about 6-7 seconds.

Version-Release number of selected component (if applicable):
3.14.1

How reproducible:
100%

Steps to Reproduce:
1. Open System Monitor
2. Try to reduce CPU usage as much as possible, wait for it to be reflected in graphs.
3. Open terminal
4. Run `yes` command.
5. Observe CPU (core) counters and CPU graphs.
6. Wait til CPU load is ovservable in graphs.
7. Stop `yes`.
8. Observe CPU (core) counters and CPU graphs. 

Actual results:
Numeric counters immediately react to executed/stopped `yes`.
Graphs curvers shows change in CPU load with delay.


Expected results:
Values of counters and graphs are in sync.


Additional info:
This problem applys to all graphs.
This problem was also in in Fedora 20. And in was realy anoying - it's more natural for people to check the shape of curves than reading numbers.

Comment 1 czerny.jakub 2014-11-21 17:00:00 UTC
Created attachment 959871 [details]
no load not yet drawn

Attachements describe states when the delay is most obvious - at the beginning and end of CPU load.

Comment 2 Fedora End Of Life 2015-11-04 14:51:36 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 3 Fedora End Of Life 2015-12-02 05:09:13 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.


Note You need to log in before you can comment on or make changes to this bug.