Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316150 - [Memory Browser] should release the rendering after the target is disconnected
Summary: [Memory Browser] should release the rendering after the target is disconnected
Status: CLOSED WONTFIX
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Ted Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 10:56 EDT by Alain Lee CLA
Modified: 2012-05-22 13:26 EDT (History)
1 user (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 Alain Lee CLA 2010-06-08 10:56:36 EDT 
1. When the target is connected, enter an valid expression to create a Traditional Rendering. 
2. After the the rendering is shown and displays the data, disconnect the targetr.

Note that the rendering is still shown and users are still able to scroll the rendering. However, no data is updated and displayed.

It would be better if we could either hide or release the rendering.
Comment 1 Alain Lee CLA 2010-06-09 13:23:03 EDT 
This works fine when the debug session is TERMINATED. However, this happended to me when the target was not CONNECTED. In our product, TERMINATE and CONNECT are not the same. We can launch a debug session with a target but the target can be manually connected or disconnected. 

After discussion with our team, we think it is ok to leave the rendering on. If users choose to go to a different address or scroll the rendering, ???? will be displayed. 

You can reject this bug.
Comment 2 Randy Rohrbach CLA 2012-05-22 13:26:56 EDT 
Per Alain's comments below I am rejecting this.

Randy