Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 443740 - [visualizer] When re-enabling load meters, a stale value is shown until the next refresh
Summary: [visualizer] When re-enabling load meters, a stale value is shown until the n...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.5   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 13:28 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:20 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2014-09-10 13:28:42 EDT 
1- start a remote debug session (remote, compared to local, allows us to see traces of the visualizer asking GDB about CPU load)
2- enable load meters in the multicore visualizer
3- change refresh speed of load meters to slow
4- disable load meters
5- re-enable load meters
=> notice that although a value for the cpu load is shown right away, there was no request to GDB.  This means stale values are being used.

As there could be a long time between steps 4 and 5, it would be better to either show "n/a" (as is done when the load meters are enabled the very first time) until the request for cpu load is sent to GDB.  An even better solution would be to request CPU values right away, as soon as the load meters are enabled, although I don't know if that is a complex thing to do.