Bug 267365

Description Andrey Loskutov 2009-03-06 09:05:21 EST

+++ This bug was initially created as a clone of Bug #89059 +++
(Bug 89059 was opened 2005-03-24 against Eclipse 3.1 M6)

I've downloaded today latest available 3.5 Eclipse I-build (I20090304-0834) and tried out of the box to install some plugins/work with it on a big workspace.

After 5 minutes I had my first "java.lang.OutOfMemoryError: Java heap space". Installing FindBugs plugin and running it for a while -> OOME is guaranteed. Of course, not only FindBugs needs memory, but this is an extreme example.

Ok, what is default today in eclipse.ini? There are still the old values from 2005:

-vmargs
-Xms40m
-Xmx256m

Can we please increase defaults to -Xmx500m or better -Xmx900m? 4 years since the last increase of max heap memory is an epoch in the IT industry, and looking at the average PC today we will find *at least* 1 Gig RAM installed (even these small unusable nettops have it :)

Increasing max heap should not hurt anybody (it is a MAX), but it saves users bad experience and admins a lot of time by NOT patching manually eclipse.ini or adding extra arguments for the startup scripts etc.

P.S.
Why 900m? Unfortunately, there are lot of Windows PC's with Sun's VM installed. Older Sun VM's cannot address more then 1000m and silently failback to 64m which is less then optimal for Eclipse ;-)