Eclipse terminating, exit code 1

Sudsy <> wrote or quoted:

[Eclipse]

> Finally, there are memory leaks such that you can only do
> a limited number of build/redeploy cycles before you get
> the OutOfMemoryError.

Install more memory - and allocate more to Eclipse on the
command line when you start it.
--
__________
|im |yler http://timtyler.org/ Remove lock to reply.

Tim Tyler

Tim Tyler wrote:
> Sudsy <> wrote or quoted:
>
> [Eclipse]
>
>
>>Finally, there are memory leaks such that you can only do
>>a limited number of build/redeploy cycles before you get
>>the OutOfMemoryError.
>
>
> Install more memory - and allocate more to Eclipse on the
> command line when you start it.

So that I'll get more cycles before running into the same
problem? Delaying the inevitable? 2 GB not enough?
Sorry, but that's not a real solution, is it?

Sudsy

Sudsy <> wrote or quoted:
> Tim Tyler wrote:
>> Sudsy <> wrote or quoted:

>> [Eclipse]

>>>Finally, there are memory leaks such that you can only do
>>>a limited number of build/redeploy cycles before you get
>>>the OutOfMemoryError.
>>
>> Install more memory - and allocate more to Eclipse on the
>> command line when you start it.
>
> So that I'll get more cycles before running into the same problem?

Exactly.

> 2 GB not enough?

You are sure you have 2GB allocated to your Eclipse JVM?
Perhaps double-check with your documentation?

> Sorry, but that's not a real solution, is it?

I never claimed I was offering something perfect.

Allocating more memory to Eclipse makes a substantial difference to
its usability here - since it spends less time almost out of memory,
less time crashing - and less time starting up.
--
__________
|im |yler http://timtyler.org/ Remove lock to reply.

Tim Tyler

Tim Tyler wrote:
<after addressing some of my points, Tim finally allows:>
> Allocating more memory to Eclipse makes a substantial difference to
> its usability here - since it spends less time almost out of memory,
> less time crashing - and less time starting up.

Thank you for your confirmation. For a moment there I thought you
were trying to blame the instability on my particular hardware/
software configuration!
But it's still a nifty development platform when it's not busy
trying to toast itself.

Sudsy