Community
Participate
Working Groups
Build Identifier: DefaultMarkerBehavior adds an adapter (problemIndicationAdapter) to the ResourceSet of the running editingDomain, but doesn't removes it on disposal. If the editing domain is shared, after the closing of the graphiti editor, this adapter lingers on, and keeps alive the DiagramEditor as long as the editing domain is alive. It also prevents the EmfService#diagToProvider WeakHashMap from freeing the diagrams, thus keeping the whole graphiti model in memory, even if it belonged in an unloaded resource. Reproducible: Always
Created attachment 215753 [details] Proposed patch Remove adapter on disposal
Thanks for pointing this out and providing the fix! I added the cleanup of the members of DefaultMarkerBehavior and therefore had to change the sequence of the dispose calls in DiagramEditor. Checked-in and pushed to Eclipse: commit e6921295af5801867f73434731c9d5ec7ff973d8 Author: mwenz <michael.wenz@sap.com> 2012-05-21 15:08:03 Committer: mwenz <michael.wenz@sap.com> 2012-05-21 15:08:03 Parent: 3041651840445ba36eb1de8f81fb5f2f261b72ce (Revert "Updated to RC1 version of Orbit") Branches: origin/master, master
Bookkeeping
Part of Graphiti 0.9.0 (Eclipse Juno)