Eclipse Community Forums: EMF » Huge DefaultOperationHistory

Home

Home » Modeling » EMF » Huge DefaultOperationHistory(DefaultOperationHistory filled with EMFOperation)

Huge DefaultOperationHistory [message #509048]

Thu, 21 January 2010 04:42

Eclipse User

Hi,

I have a DefaultOperationHistory which is full of EMFOperation :

http://img27.imageshack.us/img27/2728/stackundoredo.jpg

The contexts associated with them are WorkspaceCommandStackImpl$UndoContext.
Sometimes some of these EMFOperations have a huge retained set (keep a lot of memory).
Why all (almost all?) my command (EMF and GMF) are keep in this history with this context? and not only the context of my editor?
How can I remove them when the editor is closed?

I noticed that most of the memory took by EMFOperation is due to DiagramEventThreadSafe. is that normal? Is it needed? Can I remove the reference to the DiagramEventTreadSafe? (in order that it can be GC-ed)

thanks by advance for any hints

Regards,

Re: Huge DefaultOperationHistory [message #509102 is a reply to message #509048]

Thu, 21 January 2010 02:04

Eclipse User

Aurelien,

Given that DiagramEventBrokerThreadSafe is in, I'm wondering if this is
a GMF question rather than an EMF one? If your problem (a leak) is
reproducible in an unmodified generated GMF editor, you should open a
GMF bugzilla to describe how to reproduce it.

Aurelien Pupier wrote:
> Hi,
>
> I have a DefaultOperationHistory which is full of EMFOperation :
>
>
> The contexts associated with them are
> WorkspaceCommandStackImpl$UndoContext.
> Sometimes some of these EMFOperations have a huge retained set (keep a
> lot of memory).
> Why all (almost all?) my command (EMF and GMF) are keep in this
> history with this context? and not only the context of my editor?
> How can I remove them when the editor is closed?
>
> I noticed that most of the memory took by EMFOperation is due to
> DiagramEventThreadSafe. is that normal? Is it needed? Can I remove the
> reference to the DiagramEventTreadSafe? (in order that it can be GC-ed)
>
> thanks by advance for any hints
>
> Regards,
>
>

Re: Huge DefaultOperationHistory [message #509164 is a reply to message #509048]

Thu, 21 January 2010 09:52

Eclipse User

Ed,

thanks again for your quick answer Smile

I will post on GMF forum about this subject, in order to know why the DiagramEventThreadSafe take all this place and is still referenced.

However it doesn't explain why all these EMFOperation are still there. Maybe I registered it by inadvertance, calling some command with the wrong context, ...
Or it is ordinary that all these EMFOperations are kept in DefaultOperationHistory and what is wrong is that it kept so much memory?

I don't know exactly in which direction I have to look at.

Re: Huge DefaultOperationHistory [message #509178 is a reply to message #509164]

Thu, 21 January 2010 10:11

Eclipse User

Aurelien,

Yes, it's not clear if you've done something wrong or there's something
wrong in the framework. Without a test case, I'm not sure that can be
made clear...

Aurelien Pupier wrote:
> Ed,
>
> thanks again for your quick answer :)
>
> I will post on GMF forum about this subject, in order to know why the
> DiagramEventThreadSafe take all this place and is still referenced.
>
> However it doesn't explain why all these EMFOperation are still there.
> Maybe I registered it by inadvertance, calling some command with the
> wrong context, ...
> Or it is ordinary that all these EMFOperations are kept in
> DefaultOperationHistory and what is wrong is that it kept so much memory?
>
> I don't know exactly in which direction I have to look at.

Previous Topic:	How to define a Derived/Transient/Votaile Attribute in an EcoreModel (2.6M4)
Next Topic:	Using an EMF model for a GEF-based editor

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 20 21:11:45 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter