Eclipse Community Forums: Rich Client Platform (RCP) » Memory Leak in IEditorInput class

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » Memory Leak in IEditorInput class

Show: Today's Messages :: Show Polls :: Message Navigator

Memory Leak in IEditorInput class [message #465533]

Mon, 02 April 2007 07:04

Eclipse User

Originally posted by: seah.sherley.gmail.com

Hello everyone,
I have been using JProfiler to track for any memory leak.
To my horror, the class that implement the IEditorInput has a memory leak. I tried all ways to dispose any frame, composite windows etc but its useless.
None of the class except the class that implements IEditorInput will always be stuck in the memory over a short time.
Suppose I open 2 instance of the class that implemenent Editor Plus, IEditorInput and all the classes will increase their instance to 2. After a while, all the classes instance except IEditorInput is will be zero.
Then I open some more windows in the editor window.
IEditor input keep increase instance. Rubbish collection also no use.

How can I solve this problem?

Report message to a moderator

Re: Memory Leak in IEditorInput class [message #465616 is a reply to message #465533]

Tue, 03 April 2007 09:17

Paul Illingworth

Messages: 4
Registered: July 2009

Junior Member

Seah Sherley wrote:
> Hello everyone,
> I have been using JProfiler to track for any memory leak.
> To my horror, the class that implement the IEditorInput has a memory leak. I tried all ways to dispose any frame, composite windows etc but its useless.
> None of the class except the class that implements IEditorInput will always be stuck in the memory over a short time.
> Suppose I open 2 instance of the class that implemenent Editor Plus, IEditorInput and all the classes will increase their instance to 2. After a while, all the classes instance except IEditorInput is will be zero.
> Then I open some more windows in the editor window.
> IEditor input keep increase instance. Rubbish collection also no use.
>
> How can I solve this problem?

IEditorInput implementations should be very lightweight and only hold a
reference to the data, a key or some id to locate the data and not the
data itself. You may find that the references are being held onto in the
most recently used file menu. As well as being held in here they can ,
optionally, be persisted so that the menu can be restored on application
startup.

Regards
Paul I.

Report message to a moderator

Previous Topic:	Dynamic Help in RCP
Next Topic:	How to deal with network problem in an IM application?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 18:50:12 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter