Error occurred during initialization of vm too small initial heap

You are here : Home / Core Java Tutorials / Series of JVM and Garbage Collection (GC) in java — Best explanations ever

1) Read : How to write java program to pass VM/JVM parameters through CMD

Read :JVM Heap memory (Hotspot heap structure) with diagram in java

Also read : what all other VM parameters you can pass to java program through CMD or eclipse.

Please express your love by liking JavaMadeSoEasy.com (JMSE) on facebook, following on google+ or Twitter.

JVM (java virtual machine) in detail in java

Learn how to pass vmargs (VM parameters) to java program in eclipse?

>How Garbage Collection (GC) works internally in detail in java — BEST EXPLANATION EVER

>Marking and deleting objects for garbage collection in java — Mark and sweep algorithm

Thread Status:

Not open for further replies.

1. I was recently playing on my server with 6-8 people. I have 1gb of Ram for my server. Then while I was working on a project, my server crashed. I do not have a crash report for this unfortunately. Now whenever I try to launch it, I get the error of

   «Error occured during initialization of VM
   Too small initial heap
   Press any key to continue»

   Is it a RAM issue? If so, how can I fix this?
   My note for the batch file is

   @ECHO OFF
   SET BINDIR=%~dp0
   CD /D «%BINDIR%»
   «%ProgramFiles(x86)%Javajre7binjava.exe» -Xmx1024M -Xms1024 -jar craftbukkit.jar
   PAUSE

2. Curiously, have you restarted your computer since it crashed?

3. Yes I have restarted my computer but still nothing

4. see if changing the amount of ram helps… to do so change this: -Xmx1024M -Xms1024
   to this: -Xmx2024M -Xms2024M
   That will give it 2gb instead of 1gb

5. Okay So I changed it, tried to run the server, and got this error —
   «Error occurred during initialization of VM
   Could not reserve enough space for object heap
   Error: Could not create the Java Virtual Machine.
   Error: A fatal exception has occurred. Program will exit.
   Press any key to continue . . .»

6. You didn’t specify «M» for megabytes in your initial script on the -Xms parameter

   Also, if setting it to 2024 (ahem, correct amount for 2GB is 2048) causes the «Could not reserve enough space for object heap» error, that means your computer doesn’t have that much RAM free. If you are telling it you MUST have 2GB memory to start the program, it will tell you «sorry, that can’t happen, bro» and fail to start.

   FYI:
   -Xmx is your *maximum heap size*; the server will never be allowed to use more than this amount of RAM
   -Xms is your *initial heap size*; when the program starts it will be given this much memory (which can grow if needed up to the -Xmx limit). If there is not at least this much memory free when the program starts, it will fail (like the second error you got). Without the «M» to specify that 1024 was megabytes, you gave the server a starting allocation of 1kb which is too small (which is why you got the first error).

   Try this:

   @ECHO OFF
   SET BINDIR=%~dp0
   CD /D «%BINDIR%»
   «%ProgramFiles(x86)%Javajre7binjava.exe» -Xmx1G -Xms1G -jar craftbukkit.jar
   PAUSE

   That will give you 1GB (the same as 1024M) heap to start with, and it will never use more than that 1GB.

   
   Starrz and mmorton89 like this.
   

7. lol >_> I can’t believe I didn’t see that last time I saw this. 4am is correct lol.

8. oh wow lol i see it to now… fail

9. THANK YOU SOO MUCH FOR THE EXPLANATION AND FOR THE NEW NOTE FOR THE BATCH!!! IT WORKS PERFECTLY FINE NOW!!!

10. The trick with server administration is learn as much as you can about how everything works — one of the reasons Minecraft is such a great game is that it has inspired so many people (especially younger people) to figure out stuff like this. You now know how to pass memory-usage parameters to Java progams from the command line! Skillz, yo. Keep learning everything you can about how it all works!

    EDIT: Oh yeah, glad I could help

Thread Status:

Not open for further replies.

Disclosure: This article may contain affiliate links. When you purchase, we may earn a commission.

Cause:  the value of either -Xms or -Xmx is higher than or close to the size of physical memory, as my machine has 4GB memory.

Invalid heap size

Another scenario when the «invalid heap size» issue comes while restarting JVM is when you configure 64 bit JVM to accept the memory of more than 4GB but it’s running on a 32-bit data model. This «invalid heap size» occurs particularly in the Solaris box where J2SE installation contains both 32 bit and 64-bit J2SE implementation.

On other environments like Windows and Linux, 32 bit and 64 bit JVM are installed separately. 64 bit JVM installed on Solaris machines runs with a 32-bit model if you don’t specify either -d32 or -d64, which won’t accept a Maximum heap size of 4GB, hence «invalid heap size».

You can resolve this issue by running Solaris JVM with option -d64.  -d64 command-line option allows JVM to use a 64-bit data model if available.

public class HelloWorld{
  public static void main(String args[]){
      System.out.println("HelloWorld to Java");
  }
}

$ test@nykdev32:~ java -version
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Server VM (build 14.0-b16, mixed mode)

$ test@nykdev32:~ java -Xmx4096M HelloWorld
Invalid maximum heap size: -Xmx4096M
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.

$ test@nykdev32:~ java -d64 -Xmx4096M HelloWorld
HelloWorld to Java