Develop Reference

Insufficient memory for the Java Runtime Environment in Eclipse

There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 1048576 bytes for AllocateHeap
# An error report file with more information is saved as:
# C:\jboss-eap-services-6.4.4\bin\hs_err_pid6632.log
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
With the problem above, I'm trying to start the jboss server. I tried some steps and I could not find the right solution.

Please use the following setting to allocate the memory for the permanent location -Xms1024m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:-UseGCOverheadLimit

You can try to increase eclipse memory, you can do this in le eclipse.ini file (near eclipse executable file) or in the command line arguments :
-Xms256m
-Xmx16348m

It is JBoss (not Eclipse) that is crashing. So increasing Eclipse's memory is futile! (It might make things worse, in fact.)
The second thing to note is that you are running out of space in a native allocation request, so increasing the regular heap's size will not help. Options like the following will probably NOT help! (They might make things worse, in fact.)
-Xms1024m -Xmx1024m -XX:-UseGCOverheadLimit # USELESS
The third thing to note is that your JVM doesn't have a PermGen space, so fiddling with the PermGen size via
-XX:PermSize=512m -XX:MaxPermSize=512m # USELESS
is futile. (That is what Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 is saying.)
So what is the real problem?
Well you are running a 64-bit JRE, so it is not an architectural problem. (On a 32-bit JRE, the JVM's address space has hard limits ...)
In fact, it is a problem outside of the JVM itself. Basically, the JVM has asked the OS for more memory, and the OS has said "Nope!". I can thing of two possible explanations:
There may be a per-process "ulimit" in place, that is restricting the process size. Your JVM has requested beyond that limit.
The OS may have run out of virtual address space or mappable virtual memory. The former is unlikely. The latter typically arises because your OS doesn't have enough RAM and/or swap space. This can also happen is you are running within a virtual machine that is ... less than generous endowed with memory resources.
Now it appears that this may be happening when the JVM is trying to grow the Java heap. But either way, the problem is not the size of the Java heap.

64 bits JVM Could not reserve enough space for object heap

I have a Windows 7 laptop, with 16GB RAM. When I run multiple java servers I get OutOfMemory error, however, windows task manager shows that I still have 6GB of free physical memory left. It seems like to me that my JVM can only allocate ~2GB heap for all running java apps.
So I wrote some very simple Java code:
public class HelloWorld {
public static void main(String[] args) {
for(;;) System.out.println("Hello, World");
}
}
My -jvm version:
$ java -version
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
JAVA_HOME "C:\Program Files\Java\jdk1.8.0_111"
JRE_HOME "C:\Program Files\Java\jre1.8.0_111"
I did a simple java -Xmx256m -Xms256m HelloWorld and it worked as expected, however when I switched to java -Xmx2048m -Xms2048m HelloWorld I get the following:
Error occurred during initialization of VM
Could not reserve enough space for object heap
I tried multiple JDKs but none of them are working. Both windows and JVM are in 64 bits.
What can I do to fix this problem?

It seems like to me that my JVM can only allocate ~2GB heap for all running java apps.
That is not correct. The JVM is capable of asking for and using a >2GB heap.
It must be that Windows is restricting what the Java process can ask for. It may also be that Windows has reserved memory for multiple Java processes, but the memory is showing as free because the JVMs have not used it.
FWIW, running JVMs with lots more memory than they really need is not a good idea.
The fix?
Don't do it. Don't run lots of 2GB Java servers on your laptop, or reduce the heap size to something more reasonable. Overcommitting your memory is an attractive idea, until the JVMs start using all of the memory that you have allocated them. Then your system thrashes ...
Do it differently. You can run multiple servers in a single JVM.
Get more memory.

Just don't use -Xms2048m. It makes JVM to request a continuous 2Gb block of memory at once. Let JVM decide when to get additional mem for heap needs. In case of Windows, the effect you observe may be the result of badly aligned dlls mapped to proc virtual memory (antivirus, firewall, rootkit, virus etc), which make virtual memory fragmented. Running java from ide, using agents (with native impl) could also add hidden content to process virtual memory. A nice tool to observe a virtual memory of a process is vmmap from Microsoft Sysinternals suite

What does 'MaxRAM' JVM parameter signify?

I'm looking at the configuration of a JVM running on a linux server. when I run
java -XX:+PrintFlagsFinal | less | grep -iE 'MaxRam'
Which seems to basically print out just about every parameter the JDK knows about
I see
uint64_t MaxRAM = 137438953472 {pd product}
but I can't seem to find much documentation on this flag.
I found that "{pd product}" signifies "Platform Dependent Product: An officially supported, internal JVM option"
Anyone know exactly what this parameter signifies, or where I can read in more detail about platform specific JVM flags?
Misc details:
Java -version:
.
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
uname -a
Linux [SERVERNAME] 2.6.32-431.17.1.el6.x86_64 #1 [DATE] x86_64 x86_64 x86_64 GNU/Linux

According to Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide document the value in MaxRAM is used to calculate the Default Heap Size if no initial heapsize and max heap size is specified and contains as posted previously
Default Heap Size
Unless the initial and maximum heap sizes are specified on the command line, they are calculated based on the amount of memory on the machine. The proportion of memory to use for the heap is controlled by the command-line options InitialRAMFraction and MaxRAMFraction
[...]
The value of MaxRAM is platform-dependent.
Referring to the The Java Virtual
Machine Specification the size of the heap can change, depending of the implementation of the JVM.
The heap may be of a fixed size or may be expanded as
required by the computation and may be contracted if a larger heap becomes
unnecessary. The memory for the heap does not need to be contiguous.
A Java Virtual Machine implementation may provide the programmer or the user control
over the initial size of the heap, as well as, if the heap can be dynamically expanded or
contracted, control over the maximum and minimum heap size.
And to answer your platform specific JVM flags question:
Java HotSpot VM Options

Unable to set java heap space > 2GB on Win2008 64bit

Unable to set java heap space using -Xmx to 2GB or more even though the RAM size is 16GB.
I encounter an error saying "
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit"
This is seen while starting a Jenkins server on my Win2008 x64 machine.
Please let me know if I could change any system parameter which will allow me to allocate more memory.
Thanks

Run
java -version
and check you see
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
I expect you have a 32 bit version of java which is limited to 2 GB (as its not large address aware)

Found the fix with the help of clue given above by Neil.
Here is the full details:
Even though the machine is installed with JDK 1.7 x64 bit, Jenkins by default is not configured with this version available on the machine.
Jenkins has its own JRE bundled with the installer which is used by default.
To change it to a different JDK edit the Jenkins.xml file and modify the below value
<executable>jre\bin\java</executable>
to
<executable><jdk install path>\bin\java</executable>
This is now solved!!

Use "java -version" to ensure that your java hotspot is a 64-bit server vm.

theoretical limit for maximum heap size on 32 bit JVM is 4GB and for 64 bit JVM its 2^64
For more detail Click here

How to increase memory size to the heap of java

I want to increase heap java to avoid this error message
I have windows 7 64bit with java version
C:\Users\Rasha>java -version
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode)
java -Xms1024m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m
Error occurred during initialization of VM
Could not reserve enough space for object
Could not create the Java virtual machine.
Although I have already 6 Gigabyte memory, how to made the system to recognize them?
any suggestions for this problem?

Use the 64 bit JVM. The 32 bit JVM cannot allocate much beyond 1.5 gb (eg right about where you are having difficulties) due to need for contiguous address space. I KNOW you are using the 32 bit JVM because it says "Client VM" above, and there is no "Client VM" for 64 bit.

thank you, I found the problem, I have multi version of java which conflicts the configuration
the solution is to remove all versions and install the java 64 bit version and the space is allocated well
thank you every body