Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 488105 - [memory] Traditional and Floating Point Renderings: view is initially empty
Summary: [memory] Traditional and Floating Point Renderings: view is initially empty
Status: CLOSED DUPLICATE of bug 493035
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 9.0.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords:
Depends on: 493035
Blocks:
  Show dependency tree
 
Reported: 2016-02-19 08:46 EST by Marc Dumais CLA
Modified: 2017-12-15 13:07 EST (History)
4 users (show)

See Also:

Attachments
see other attachment (18.14 KB, image/png)
2016-02-19 08:46 EST, Marc Dumais CLA 		no flags Details
empty view (22.79 KB, image/png)
2016-02-19 10:12 EST, Marc Dumais CLA 		no flags Details
Show Obsolete (1) View All 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 Dumais CLA 2016-02-19 08:46:31 EST 
Created attachment 259825 [details]
see other attachment

This happens in both the Memory and Memory Browser views, for Traditional and Floating Point renderings. 

When a new Memory Browser view is created, or when a new rendering is created in the Memory view using one of these renderings, the view is initially not populated. It then becomes populated when a refresh occurs, for example by re-sizing the view. See attached screenshot for an example.
Comment 1 Marc Dumais CLA 2016-02-19 10:12:00 EST 
Created attachment 259829 [details]
empty view
Comment 2 Jonah Graham CLA 2016-08-09 13:32:45 EDT 
+1 I just ran into this too. It is (related?) to GTK3 for me as it is fully reliably reproduced with GTK3 but does not happen with GTK2. (This is on Neon, so I updated Version from Next to 9.0.0, I haven't tested in older versions.)
Comment 3 Marc-André Laperle CLA 2017-12-15 13:07:56 EST 

*** This bug has been marked as a duplicate of bug 493035 ***