Eclipse won't start, eclipse.ini -Xmx512m changes it self to -Xmx1000m after Eclipse closes and makes it again not executable next time, so I have to change elipse.ini again back to -Xmx512m.
It happens when I check the updates, installed plugins etc. and turn on/off computer.
It's second morning it got changed, kind of like every morning after I installed chronon.
Any idea how to tell chronon or eclipse not to touch my eclipse.ini, it's a not a file to play with.
Based on your comments, we just released an update of Chronon, 1.3.2 which sets the -Xmx value to only 900m for 32 bit machines.
Please update now and let me know if everything works fine, so that this issue can be marked closed.
sure, it happened yesterday morning, I was going though code the evening before, find out it's a -Xmx valut being too high, so I reverted to my old one, worked again yesterday, was checking plugins etc. but today morning again the same problem :|
Microsoft Windows XP [Version 5.1.2600]
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Everything is 32bit.
Well 1000m is way too high for my system obviously, got 2GB ram, tried the 512m value and runned lot's of other applications so I had under 512MB ram free but elipse started alright, so java vm can't handle 1000m on my system.
well the Xmx value is independent of the actual ram on your system. it only 'allows' the jvm to use the extra memory if needed.
We tried to push it to 1000m which is under the limit of 1.2gb allowed by the 32bit jvm.
it seems the problem is on win xp only.
Could you please try setting it to say -Xmx950m and see if eclipse still runs?
If it works we can change the installer to make that the Xmx instead of 1000m.
It will also help all the other people who are probably facing the same problem as you.
found that p2.inf file with 1000m also, changed it to 640m, updated, but the eclipse.ini was again 1000m, well it starts after update but when I looked at the ini it was changed to 1000m, so closed and it didn't started again.
the p2.inf is set to 900m though
dunno maybe something else is setting my ini to 1000m after updates, but the update done was only chronon, nothing else was there available anyway
try doing a 'garbage collection' of your eclispe plugins.
This will ensure that all the plugins you removed/updated are fully cleared from the eclipse directory.
Run the following from the command line:
C:\eclipse\eclipsec.exe -application org.eclipse.equinox.p2.garbagecollector.application -profile epp.package.java
Error, log file:
!SESSION 2011-06-09 14:22:09.640 -----------------------------------------------
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=cs_CZ
Framework arguments: -product org.eclipse.epp.package.jee.product -application org.eclipse.equinox.p2.garbagecollector.application -profile epp.package.java
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -application org.eclipse.equinox.p2.garbagecollector.application -profile epp.package.java
!ENTRY org.eclipse.osgi 4 0 2011-06-09 14:22:14.640
!MESSAGE Application error
java.lang.IllegalArgumentException: "epp.package.java" is not a valid profile identifier.
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
there was one other place where 1000m was mentioned, so I've got rid of it:
#Thu Jun 09 14:00:36 CEST 2011
used to be
To fix the error with that command, you gotta choose the correct profile name for the profile argument, which i guess is different for you from the usual one i specified.
To find , open the eclipse\configuration\config.ini file and check the value of eclipse.p2.profile property.
Put the correct profile name and run that command again.
well a real quick way to test it is to manually set the -Xmx value in eclipse.ini to something below 900, say 512m.
Then try installing Chronon. If it works, you are set for good.
The eclipse.ini file is modified by Chronon (or any other plugin) only if the new -Xmx value is greater than the current value specified in the file.