Loading Profile...
Twitter, 
Facebook, or email.
I’m undecided
JVM creation failed on chronon installation
Looks like I can't increase my eclipse Heap memory more than 384m, installing Chronon sets this to 1100. Doing this will fail JVM creation. Is there a workaround for this?
Official Responses
-
For people looking at this issue, I am updating it just to note that this bug was present only during the beta releases and has been solved ever since.
Chronon installation should not crash eclipse/jvm anymore. -
You can edit the 'eclipse.ini' file located in your eclipse root directory, to change the memory to whatever you want. In this case you will need to modify the -Xmx value in the eclipse.ini file.
That said, Chronon needs the extra memory in order to function properly.
It is unusual for a jvm to allow only 384 max memory. Which jvm and platform are you running on?
Try lowering the memory to 1000m instead of 384m and see if it runs?
EMPLOYEE-
You can edit the 'eclipse.ini' file located in your eclipse root directory, to change the memory to whatever you want. In this case you will need to modify the -Xmx value in the eclipse.ini file.
That said, Chronon needs the extra memory in order to function properly.
It is unusual for a jvm to allow only 384 max memory. Which jvm and platform are you running on?
Try lowering the memory to 1000m instead of 384m and see if it runs?Comment -
-
Satish,
Was the problem was eventually solved? -
-
I'm having a problem in this category too. After getting it to work with my applet, when I shut down the applet cleanly, Chronon gives me an out of heap space error in the Shutdown hook during data compression.
My -Xmx value for Eclipse is at 1024m. Any higher than that and the Eclipse JVM fails to start.
EDIT: Strike that. Even though I'm running the Java Applet from within Eclipse (via Applet Viewer), since Chronon doesn't appear to support applets, I have to specify the VM arguments explicitly. Thus, it's the same as running an external app, and increasing Eclipse's memory won't help.
Instead, I added Xmx and Xms arguments to increase memory allocated to the Applet Viewer, and the heap size problems went away. -
-
For people looking at this issue, I am updating it just to note that this bug was present only during the beta releases and has been solved ever since.
Chronon installation should not crash eclipse/jvm anymore. -
EMPLOYEE
