Bug 227263

jedit also would not work.  After I installed sun 1.5.0 java devel, both apllication could be run and do not show problems.

I got this one with current factory too!

# eclipse
JVM terminated. Exit code=1
/usr/bin/java
-Xms64M
-Xmx256M
-jar /usr/share/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /usr/share/eclipse/eclipse
-name Eclipse
-showsplash 600
-exitdata 600006
-data /home/felix/.eclipse
-vm /usr/bin/java
-vmargs
-Xms64M
-Xmx256M
-jar /usr/share/eclipse/startup.jar

I the konsole I see the following:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

playing a little bit with it I found out that "eclipse -vmargs -Xmx64M -Xms64M" works.

The other values come from "/etc/eclipse.conf".

I have a notebook with 512MB RAM, this is quiete common and should be enough to run eclipse!

eclipse -vmargs -Xmx64M -Xms64M does not work reproducable ... ;(

I have downloaded eclipse-SDK-3.2.2-linux-gtk.tar.gz from eclipse.org and it has been working all the time for now. It does no change the memory-options:
/usr/bin/java -Xms40m -Xmx256m -jar /home/felix/Desktop/./eclipse/startup.jar -os linux -ws gtk -arch x86 -launcher /home/felix/Desktop/./eclipse/eclipse -name Eclipse -showsplash 600 -exitdata 1a8004 -vm /usr/bin/java -vmargs -Xms40m -Xmx256m -jar /home/felix/Desktop/./eclipse/startup.jar

The openSUSE eclipse does not work with the VM_ARGS uncommented.
# rpm -qa | grep eclipse
eclipse-platform-3.2.1-45
eclipse-swt-3_2-gtk2-3.2-0.pm.2
eclipse-gtk2-3.2.1-45
eclipse-scripts-3.2.1-45
eclipse-3.2.1-45
eclipse-jdt-3.2.1-45

It works for me since one of the last factory updates ... 

For the record:
felix@linux-95zp:~> rpm -qa | grep eclipse
eclipse-swt-3_2-gtk2-3.2-0.pm.2
eclipse-platform-3.2.1-47
eclipse-jdt-3.2.1-47
eclipse-gtk2-3.2.1-47
eclipse-3.2.1-47
eclipse-scripts-3.2.1-47
felix@linux-95zp:~> rpm -qa | grep java
java-1_4_2-gcj-compat-1.4.2.0-88
java-1_5_0-sun-plugin-1.5.0_update11-4
java-1_5_0-sun-1.5.0_update11-4
java-1_5_0-sun-devel-1.5.0_update11-4
java-1_5_0-sun-alsa-1.5.0_update11-4

I have no idea what change cured it for me ...

mmm ... should we close this bug then?
I can't reproduce it here neither

I tested with openSUSE 10.3 alpha 3 and had no problems installing and using eclipse.

ok ... closing this for now, please re-open if the problem should occur again.
Thanks,
Daniel

I am sad to report that the problem is there again. I have used eclipse on Sunday, therefore it must be from one of the factory updates since Monday 16.

java-1_5_0-sun-plugin-1.5.0_update11-5
java-1_5_0-sun-1.5.0_update11-5
java-1_5_0-sun-alsa-1.5.0_update11-5
java-1_5_0-sun-devel-1.5.0_update11-5
java-1_4_2-gcj-compat-1.4.2.0-91

eclipse-3.2.1-49
eclipse-swt-3_2-gtk2-3.2-0.pm.2
eclipse-scripts-3.2.1-49
eclipse-jdt-3.2.1-49
eclipse-gtk2-3.2.1-49
eclipse-platform-3.2.1-49

kernel-default-2.6.21_rc6_git4-2

# eclipse
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

JVM terminated. Exit code=1
/usr/lib/jvm/java/bin/java
-Xms64M
-Xmx256M
-jar /usr/share/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /usr/share/eclipse/eclipse
-name Eclipse
-showsplash 600
-exitdata 350006
-data /home/felix/.eclipse
-vm /usr/lib/jvm/java/bin/java
-vmargs
-Xms64M
-Xmx256M
-jar /usr/share/eclipse/startup.jar

playing again with it:

# eclipse
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

while this works!
# java -jar /usr/share/eclipse/startup.jar

It is still the same

# java -jar /usr/share/eclipse/startup.jar 
works.

# eclipse
does not!

Hi Felix.
Thanks for keeping looking at this. Lately I was busy updating eclipse to the next release which is why I did not fix stuff on the old release.
I will test whether this works on my machine and come back to you.

Hi.
I set VM_ARGS in eclipse.ini to
VM_ARGS=""
to avoid that the VM tries to allocate more memory than available.
Eclipse still starts fine here then.
Please reopen the bug if the problem remains for versions >= 3.3M3

Thanks and sorry that it took rather long before I changed this setting.

Regards,
Daniel

This issue pops up again on openSUSE 10.3 Goldmaster (x86-64). 

I can confirm that 10.3 GM 32bits still has this annoying problem.
Using Eclipse with Aptana plugins and openSUSE 10.3 32bits with all the online updates.
Version: 3.3.0
Build id: I20070625-1500
I keep getting "Out of memory error" every 10 minutes, it is unusable.

I changed my /usr/share/eclipse/eclipse.ini to 
-showsplash
org.eclipse.platform
-vmargs
-Xms512m
-Xmx1024m

but didn't make any change. I tried starting using:

eclipse -vmargs -Xmx64M -Xms64M

but it doesn't help either. I also see that my /etc/eclipse.conf has this:

# The directory where to find the workspace by default.
USER_DIR="$HOME/.eclipse"

# The JVM to use. If you have jpackage-utils installed, you shouldn't set this.
#JAVACMD=""

# Arguments to pass to the JVM.
VM_ARGS=""

Please let me know if you need more information

Something interesting I found out is that when I read my configuration details, it doesn't show the arguments that the eclipse.ini has. I'll attach my Configuration Details. Also when I pass the arguments directly using (for example):

eclipse -vmargs -Xmx64M -Xms64M

those arguments don't show up in the configuration details either. The only time the arguments show up in the configuration details is when I edit the file /usr/share/eclipse/eclipse and I add them in this line:

/usr/share/eclipse/eclipse.bin -startup $STARTUP_JAR "" -vmargs -Xms512m -Xmx1024m 

And doing this the problem is gone. Why is the eclipse.ini file being ignored in the first place? or why are the arguments passed in the command line also being ignored? I think they shouldn't, should they?

Created attachment 186005 [details]
Configuration Details

Configuration Details don't contain the arguments that the eclipse.ini file has nor the arguments being passed as arguments in the command line

Hi.
Try having your eclipse.ini being:

-showsplash
org.eclipse.platform
-vmargs
-Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-XX:PermSize=128m


assigning to Java team

I had the same bug with Eclipse.

I fixed the problem by downgrading my x.org installation using the SUSE 10.3 installation DVD.

Eclipes always worked until a recent automatic update which also updated 
my xorg installation.

It would be helpful to be informed when xorg can be updated again without creating conflicts with Eclipse

I think it's fixed. I cannot reproduce it. I'm closing the bug, please re-open if the problem should occur again. Thank you