Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316150

Summary:	[Memory Browser] should release the rendering after the target is disconnected
Product:	[Tools] CDT	Reporter:	Alain Lee <a-lee>
Component:	cdt-memory	Assignee:	cdt-debug-inbox <cdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Ted Williams <ted>
Severity:	normal
Priority:	P3	CC:	Randy.Rohrbach
Version:	7.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Alain Lee

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

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

2012-05-22 13:26:56 EDT

Per Alain's comments below I am rejecting this.

Randy