|Session properties and memory leak [message #632493]
||Wed, 13 October 2010 08:01
| Cyril Chéné
Registered: July 2009
My plugin defines a huge model that is stored in a project session properties. From time to time, the model instance is replaced by another instance in the project session properties.
I found that it ended with an OutOfMemoryError...
A little profiling showed me that old instances of my model are kept by two different objects :
- The org.eclipse.core.internal.resources.SaveManager instance through the lastSnap attribute (of type ElementTree). The tree path ends with a DataDeltaNode whose data attribute is a ProjectInfo instance that retains the session properties
- The oldState of my plugin's builder, who is kept by the Workspace instance through its tree attribute (exact path is workspace.tree.lookupCache.data.description.buildSpec.builde r.oldState)
I understand that the first is the resource local history. But what is the second?
And can anybody tell me if :
- it is normal to have these Session Properties kept ?
- there is a way to get rid of them ?
PS: I'm using Eclipse 3.2.2, I know it's old, but that's the way it is...
Powered by FUDForum
. Page generated in 0.01850 seconds