Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316652 - [memory] MemoryViewSynchronizationService's fSyncServiceProvider not updated when switching between Memory Monitors
Summary: [memory] MemoryViewSynchronizationService's fSyncServiceProvider not updated ...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-11 16:22 EDT by Justin Kong CLA
Modified: 2019-11-14 03:51 EST (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 Justin Kong CLA 2010-06-11 16:22:00 EDT 
Build Identifier: 

Whenever a memory rendering is selected, it's #activated method is called, causing it to be set as the fSyncServiceProvider for the MemoryViewSynchronizationService. 

However, when switching between Memory Monitors, the #activated method will not be called for any of the renderings in the current Memory Monitor. This can result in a situation where the fSyncServiceProvider is set to a rendering that is currently hidden, meaning that any PropertyChangeEvents for the current Memory Monitor will not be captured.

Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-14 03:51:23 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.