Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Memory is exhausted quickly during development
Memory is exhausted quickly during development [message #504229] Thu, 17 December 2009 18:35 Go to next message
Setya Nugdjaja is currently offline Setya NugdjajaFriend
Messages: 567
Registered: July 2009
Senior Member
Hi all,

During intensive development of RAP application in which I run
RAP JUnit mercilessly, the memory consumption is piling up quickly not
to mention the tests run slower and slower after each run. Usually after
quite sometime we have to restart Eclipse. This is counterproductive and
distractive.

Has anybody experienced the same problem ?

Any advice would be greatly appreciated.


Regards,

Setya
Re: Memory is exhausted quickly during development [message #504345 is a reply to message #504229] Fri, 18 December 2009 12:46 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
I have a vaguely remember that the internal browsers leaks memory
(at least IE on Windows) but I couldn't find a bug or other proof
for that.
Did you try to run the tests in the external browser?

On 17.12.2009 19:35, Setya wrote:
> Hi all,
>
> During intensive development of RAP application in which I run
> RAP JUnit mercilessly, the memory consumption is piling up quickly not
> to mention the tests run slower and slower after each run. Usually after
> quite sometime we have to restart Eclipse. This is counterproductive and
> distractive.
>
> Has anybody experienced the same problem ?
>
> Any advice would be greatly appreciated.
>
>
> Regards,
>
> Setya
>
>
Re: Memory is exhausted quickly during development [message #504361 is a reply to message #504345] Fri, 18 December 2009 13:36 Go to previous messageGo to next message
Setya Nugdjaja is currently offline Setya NugdjajaFriend
Messages: 567
Registered: July 2009
Senior Member
Hi,

> I have a vaguely remember that the internal browsers leaks memory (at
> least IE on Windows) but I couldn't find a bug or other proof for that.
> Did you try to run the tests in the external browser?

I'm developing on Ubuntu, so the default browser is Firefox I guess. I
only try on external browser occasionally.

Before each test run I seldom shutdown OSGI from previous run first.
Could this be the cause ?


Setya
Re: Memory is exhausted quickly during development [message #504362 is a reply to message #504361] Fri, 18 December 2009 13:50 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
On 18.12.2009 14:36, Setya wrote:
> Hi,
>
>> I have a vaguely remember that the internal browsers leaks memory (at
>> least IE on Windows) but I couldn't find a bug or other proof for that.
>> Did you try to run the tests in the external browser?
>
> I'm developing on Ubuntu, so the default browser is Firefox I guess. I
> only try on external browser occasionally.
>
> Before each test run I seldom shutdown OSGI from previous run first.
> Could this be the cause ?
If you leave the default settings as is, a possibly running OSGi
instance will be killed before the next one is launched. But as the
OSGi instance is running in a separate VM, this would not affect the
memory consumption of your IDE.


>
>
> Setya
Re: Memory is exhausted quickly during development [message #504365 is a reply to message #504362] Fri, 18 December 2009 14:31 Go to previous messageGo to next message
Setya Nugdjaja is currently offline Setya NugdjajaFriend
Messages: 567
Registered: July 2009
Senior Member
Rudiger,

> If you leave the default settings as is, a possibly running OSGi
> instance will be killed before the next one is launched.

I thought the default settings is with VM argument
-Dosgi.noShutdown=true, doesn't it mean that the previous one is kept
alive ?

Also I notice that after each run, a new Java process is created using
approx. 150Mb and it stays there forever until I shutdown the OSGI instance.

> But as the OSGi
> instance is running in a separate VM, this would not affect the memory
> consumption of your IDE.

Sorry, I mean it slows down the whole machine and eventually hurts Eclipse.


Regards,

Setya
Re: Memory is exhausted quickly during development [message #504367 is a reply to message #504365] Fri, 18 December 2009 14:42 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
On 18.12.2009 15:31, Setya wrote:
> Rudiger,
>
>> If you leave the default settings as is, a possibly running OSGi
>> instance will be killed before the next one is launched.
>
> I thought the default settings is with VM argument
> -Dosgi.noShutdown=true, doesn't it mean that the previous one is kept
> alive ?
>
> Also I notice that after each run, a new Java process is created using
> approx. 150Mb and it stays there forever until I shutdown the OSGI
> instance.
I was referring to "Terminate possibly running previous launch" on
the "Main" tab.

>
>> But as the OSGi instance is running in a separate VM, this would not
>> affect the memory consumption of your IDE.
>
> Sorry, I mean it slows down the whole machine and eventually hurts Eclipse.
>
>
> Regards,
>
> Setya
Re: Memory is exhausted quickly during development [message #504372 is a reply to message #504367] Fri, 18 December 2009 14:51 Go to previous messageGo to next message
Setya Nugdjaja is currently offline Setya NugdjajaFriend
Messages: 567
Registered: July 2009
Senior Member
Hi,

> I was referring to "Terminate possibly running previous launch" on the
> "Main" tab.

Yes, this option is always checked. So I guess its the OSGI instances
that are piling up.


Setya
Re: Memory is exhausted quickly during development [message #504373 is a reply to message #504372] Fri, 18 December 2009 15:00 Go to previous message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
If you are running the *same* launch configuration, there should be
one such instance at most.
Feel free to file a buzilla if this is not the case.


On 18.12.2009 15:51, Setya wrote:
> Hi,
>
>> I was referring to "Terminate possibly running previous launch" on the
>> "Main" tab.
>
> Yes, this option is always checked. So I guess its the OSGI instances
> that are piling up.
>
>
> Setya
Previous Topic:Problem with perspective change after last update [20091214]
Next Topic:Form Header is not rendered correctly
Goto Forum:
  


Current Time: Thu Apr 25 08:18:50 GMT 2024

Powered by FUDForum. Page generated in 0.04284 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top