We do set the value to 1000m when you install chronon, so that chronon can make use of that extra memory.

However, the jvm shouldnt crash due to it.

Can you tell me which platform and which exact version of the jvm you are running?

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]
sp3, en

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.

[code]-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
c:/Program Files/Java/jdk1.6.0_22/bin/javaw.exe
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms128m
-Xmx512m
[/code]

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.

-Xmx914m

is the max that will run on my system, 915m will not run, nor 950m

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
units.1.instructions.configure=org.eclipse.equinox.p2.touchpoint.eclipse.addJvmArg(jvmArg:-Xmx900m);

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 -----------------------------------------------
eclipse.buildId=M20110210-1200
java.version=1.6.0_22
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
!STACK 1
java.lang.IllegalArgumentException: "epp.package.java" is not a valid profile identifier.
at org.eclipse.equinox.internal.p2.garbagecollector.Application.start(Application.java:51)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

---
there was one other place where 1000m was mentioned, so I've got rid of it:

c:\_app\_development\eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.jee.profile\.data\org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions\jvmargs

#Thu Jun 09 14:00:36 CEST 2011
-Xms=40m,40m
eclipse.userDefined\:-Xms=128m
-Xmx=384m,512m,768m,900m
eclipse.userDefined\:-Xmx=640m

used to be
-Xmx=384m,1000m,512m,900m

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.

yes that helped to run the eclipsec.exe

will see if the 1000m gets set somehow again, if it changes to 900m at least I know chronon set it again