Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327733 - Memory leak in MetaDataModelManager
Summary: Memory leak in MetaDataModelManager
Status: RESOLVED FIXED
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Carlin Rogers CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-14 01:07 EDT by Carlin Rogers CLA
Modified: 2010-10-14 13:21 EDT (History)
1 user (show)

See Also:

Attachments
patch to override destroy() (1.03 KB, patch)
2010-10-14 01:33 EDT, Carlin Rogers CLA 		no flags Details | Diff
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 Carlin Rogers CLA 2010-10-14 01:07:44 EDT 
The MetaDataModelManager which is an object manager (instances of MetaDataModel for each project) via the ResourceSingletonObjectManager framework, does not clean up resources when the project is deleted. This ends up leaking MetaDataModel objects and underlying data. Though there is no persistent data to clean up, MetaDataModelManager should still override the IManagedObject.destroy() method and clean up resources and memory references.
Comment 1 Carlin Rogers CLA 2010-10-14 01:33:34 EDT 
Created attachment 180849 [details]
patch to override destroy()
Comment 2 Carlin Rogers CLA 2010-10-14 13:21:01 EDT 
Checked in the patch to HEAD, revision 1.21 of MetaDataModelManager.