Eclipse Community Forums: GMF (Graphical Modeling Framework)

Home » Modeling » GMF (Graphical Modeling Framework) » GMF Diagram and Memory

GMF Diagram and Memory [message #153562]

Fri, 05 October 2007 02:52

Eclipse User

Originally posted by: swanbrook66.gmail.com

Hi,
I have a relatively large GMF application which I recently profiled
using JProfiler. One thing that struck me immediatley is that all the
objects created when I open a diagram (edit parts, edit policies, etc,
etc) are never garbage collected. These objects hang around in memory
for the time the application is open. If I reopen the diagram, they all
get created again so this is obviously a huge memory leak.
I was wondering if this is a general problem in GMF for people or would
it be something that I am doing myself by accident. I have checked the
dispose() method in my GRaphicalEditor class and it does call
super.dispose() before doing some custom tidy-up stuff.
Sorry if this has been talked about before but I am fairly new to GMF
and couldn't find and references to GMF and memory when I searched these
groups.

Any info much appreciated.
Thanks.

Re: GMF Diagram and Memory [message #155384 is a reply to message #153562]

Mon, 15 October 2007 10:49

Eclipse User

Tom,

The Runtime Team has certainly profiled GMF applications built on the
runtime portion of GMF before, but there may have been a regression.

I would suggest trying to reproduce the problem with one of the GMF
Examples and narrowing down the problem to the runtime portion (i.e.
geoshapes and logic diagrams) or the generated code (i.e. mindmap and
taipan diagrams) and then submitting a bug report.

Regards,
Cherie

Tom Jones wrote:
> Hi,
> I have a relatively large GMF application which I recently profiled
> using JProfiler. One thing that struck me immediatley is that all the
> objects created when I open a diagram (edit parts, edit policies, etc,
> etc) are never garbage collected. These objects hang around in memory
> for the time the application is open. If I reopen the diagram, they all
> get created again so this is obviously a huge memory leak.
> I was wondering if this is a general problem in GMF for people or
> would it be something that I am doing myself by accident. I have checked
> the dispose() method in my GRaphicalEditor class and it does call
> super.dispose() before doing some custom tidy-up stuff.
> Sorry if this has been talked about before but I am fairly new to GMF
> and couldn't find and references to GMF and memory when I searched these
> groups.
>
> Any info much appreciated.
> Thanks.

Re: GMF Diagram and Memory [message #205779 is a reply to message #155384]

Wed, 17 September 2008 10:57

Eclipse User

Is any updates on this? I have the same issue.
Edit part objects is not destroyed after close diagram.

Re: GMF Diagram and Memory [message #207852 is a reply to message #205779]

Mon, 06 October 2008 00:47

Eclipse User

Hi there,
We have also been facing identical issues. I have tried to use JMap and
JHat to analyze the leaks, although I have not had any success with
finding the root cause as there is a huge amount of data to deal with even
for a 19 MB heap dump.

Has anyone had any luck?

Thanks,
Sriram
P.S.: Just to give a brief background, we are developing a multi page
graphical editor. The application makes use of EMF, GEF and GMF.

Re: GMF Diagram and Memory [message #207859 is a reply to message #205779]

Mon, 06 October 2008 01:59

Eclipse User

Hello there,
I am also facing the same problem and have not been able to get anywhere.
Using JMap and JHat was not very useful as the number of objects to deal
with is very big even for a 19MB heap dump.

Thanks
Sriram
P.S.: My application is a multi page graphical editor and makes use of
EMF, GMF and GEF

Previous Topic:	Create connection popup menu override?
Next Topic:	Diagram Editor opens up very slowly

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 01:45:21 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter