Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345476 - LaunchVMProvider does not dispose of DefaultVMModelProxyStrategy
Summary: LaunchVMProvider does not dispose of DefaultVMModelProxyStrategy
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 13:45 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:26 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 2011-05-11 13:45:03 EDT 
According to the java memory tool, DefaultVMModelProxyStrategy is not being cleaned-up for DSF-GDB's LaunchVMProvider.  I don't see DefaultVMModelProxyStrategy being uninstalled for that provider and I've confirmed that DefaultVMModelProxyStrategy.dispose() is not called for that case.

Pawel wrote:

It's a bug.  We currently dispose model proxies when the proxies are not 
active, and there is no cache entries associated with it.  But all 
proxies should be disposed when it's owning VM Provider is disposed.