Develop Reference

"insufficient memory for the Java Runtime Environment " message in eclipse

When I run my Java code in Eclipse, I get the following message:
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (malloc) failed to allocate 4088 bytes for AllocateHeap
An error report file with more information is saved as:
E:\Eclipse_Workspace\BTest\hs_err_pid1888.log
I have 4GB RAM in my computer. I have changed my JRE from 1.7 to 1.8 too. But the issue seems un-resolved. I use a Win 8 system with i3 Processor and have around 20gb of free disk space in my C Drive.
Eclipse version: Eclipse Juno Service release 2
I also get this message while starting Eclipse. I have attached the error message screen shot.
What is causing this issue?
Memory parameters in "eclipse.ini" file:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx512m
Resolution:
Re-installing eclipse fixed the problem.

The message above means that you're running so many programs on your PC that there is no memory left to run one more. This isn't a Java problem and no Java option is going to change this.
Use the Task Manager of Windows to see how much of your 4GB RAM is actually free. My guess is that somewhere, you have a program that eats all the memory. Find it and kill it.
EDIT You need to understand that there are two types of "out of memory" errors.
The first one is the OutOfMemoryException which you get when Java code is running and the Java heap is not large enough. This means Java code asks the Java runtime for memory. You can fix those with -Xmx...
The other error is when the Java runtime runs out of memory. This isn't related to the Java heap at all. This is an error when Java asks the OS for more memory and the OS says: "Sorry, I don't have any."
To fix the latter, close applications or reboot (to clean up memory fragmentation).

How to diagnose this error even when running the simple command:
java -version
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# An error report file with more information is saved as:
# /home2/ericlesc/code/java/c2/hs_err_pid23944.log
Check the amount of free memory you have:
free -m
total used free shared buffers cached
Mem: 28119 26643 1475 189 2391 15368
-/+ buffers/cache: 8884 19235
Swap: 5117 34 5083
Check the max number of user processes, make sure you are not over limit:
ulimit -a
ps -ef | wc -l
For me, the reason this happened was because PHP had consumed too much memory allocated to me on bluehost, and the way I was able to fix it, without restarting PHP or the server ( I can't ) was to take the public_html directory and rename it. And give it a minute for PHP to see the change, then rename it back.
A bug in the php engine itself. I found a clever way to give the PHP engine a swift kick.
(update Feb 2016) (I'm getting a spike of up-votes on this because Bluehost instance PHP engines are reserving all the memory and leaving none for the JVM. In their defense, PHP is evolving into an unholy rube Goldberg machine. Bluehost as a service is on the decline.

If you are on ec2 and wanted to do mvn build then use -T option which tells maven to use number of threads while doing build
eg:mvn -T 10 clean package

If you are using Virtual Machine (VM), allocate more RAM to your VM and your problem will be solved.

In your Eclipse installation directory you should be able to find the file eclipse.ini. Open it and find the -vmargs section. Adjust the value of:
-Xmx1024m
In this example it is set to 1GB.

Try to modify your eclipse.ini with below
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms2G
-Xmx3G
-XX:MaxPermSize=2G
-XX:+UseCompressedOops
-XX:+UseParallelGC
Once you open your eclipse you can try below
Looks like your application consumes more memory than allocated (Default). I will try two things
As suggested by Harmlezz increase your memory allocation to JVM to -Xms2g -Xmx2g (If needed increase it more and try it out)
Download eclipse memory analyzer and check for what causing memory leak OR even you can use JConsole to see JVM memory utilization in order to figure out application memory leak issue.

It is quite simple to fix, I am not sure why no one mentioned the actual working solution.
Firstly, make sure, Wireless Hotspot is Turned Off. That's most important, while building the Project, the Hotspot must not be On.
Do this, and Thanks me later 💖
Secondly, set the Environment Variables into your system, and Thirdly disable the firewall or antivirus for Android Studio & Java VM. It will definately fix your issue.
Starting Gradle Daemon...
Gradle Daemon started in 4 s 291 ms
Starting Gradle Daemon...
Gradle Daemon started in 5 s 664 ms
Starting Gradle Daemon...
Gradle Daemon started in 2 s 210 ms
Starting Gradle Daemon...
Gradle Daemon started in 7 s 258 ms

In my case it was that I manually set the Windows virtual memory too low to save space in the system SSD.

You need to diagnosis the jvm usages like how many process is running and what about heap allocation. there exists a lot of ways to do that for example
you can use java jcmd to check number of object, size of memory (for linux you can use for example "/usr/jdk1.8.0_25/bin/jcmd 19628 GC.class_histogram > /tmp/19628_ClassHistogram_1.txt", here 19628 is the running application process id). You can easily check if any strong reference exists in your code or else.

I know the question talking about eclipse but i got the similar issue many times with Intellij as well and the solution for it was easy .. Just run the 64 bit exe not the 32 one which is always the default one.

In my case it was that the C: drive was out of space. Ensure that you have enough space available.

STS taking long time to start

Can any one please suggest, Why STS(Version: 3.4.0.RELEASE) taking long time to start.
My PC Deatails:
Window 7,
Ram : 4GB,
i3 processor,
32 bit O.S
STS.ini Details:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130807-1835
-product
org.springsource.sts.ide
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vmargs
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.browser.IEVersion=10001
I already searched for this issue but i can't got any good solution,any help is really appreciated.

May be you can try following
Increase from -Xms40m to -Xms500m. It indicates jvm to start with 500 Mb memory.
Try with STS –clean
Remove file <WORK_SPACE>/.metadata.plugins\org.eclipse.core.resources.projects\.markers.snap, because sometimes eclipse will constantly polling a fairly large snapshot of some of your projects.
You can disable ‘Refresh workspace on startup’ option in Windows -> Preferences -> General -> Startup and Shutdown
Disable automatic builds under Install/updated and Label Decorator
Upgrading to the latest JVM supported on your machine this may help as well
Disable all validations under preferences unless you need them
I hope these tips will help you for sure :) .

My STS was taking a long time, 5 minutes just to boot up, in spite of running on a high performance SSD machine. So I modified the STS.ini with Xms=200m(original value was 40m) and it started booting up real fast in under 30 seconds.
-Dosgi.requiredJavaVersion=1.8
--add-modules=ALL-SYSTEM
-Xms300m
-Dosgi.module.lock.timeout=10
-Dorg.eclipse.swt.browser.IEVersion=10001
-Xmx1200m

STS is based off eclipse so some the answers on this site re speeding up eclipse will help.
I noticed a great speed up by installing a Solid State Drive. This
speeds up your whole machine.
Using the latest oracle JDK speeds things up for me too.

Eclipse + GWT -> Out of memory in development mode

If I run my GWT application in eclipse in development mode and click around in the browser for some time, I always get an "out of memory" error in eclipse. My computer has 16 GB Ram, and there is never used more than 8GB.
I tried several config parameters. The VM-arguments in my Run configuration contain these parameters: "-Xms8192m -Xmx8192m"
Even in the eclipse.ini I tested several config parameters and now it looks like this:
--launcher.XXMaxPermSize
8192M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
8192m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms8192m
-Xmx8192m
But I still get the error. Is there any way to prevent this?

If the browser application is throwing the OutOfMemoryError, then you don't need to change the Eclipse settings (eclipse.ini), that's only for Eclipse itself (more memory, usually faster workbench).
To increase an app's memory (any Java app launched from Eclipse), go to the Run/Debug configurations... in the Run menu and set the VM arguments on the Arguments tab of the app's run config:
-Xms128M -Xmx1024M -XX:MaxPermSize=256M

put this in vm arguments in your run configurations:
-Xmx2048M -XX:MaxPermSize=512m

If I run my GWT application in eclipse in development mode and click around in the browser for some time, I always get an "out of memory" error in eclipse.
Not exactly sure what the problem is but I do see some issues with your current arguments.
You have 2 launcher args that are the same. You don't need the 2nd entry of:
--launcher.XXMaxPermSize
8192M
I really doubt that you want 8g of PermSize. Something like 512m is probably much better. You can use jconsole to see how much memory is in the perm space bucket. In the below image taken from jconsole's memory tab, the bar highlighted at the bottom right shows the "Perm Gen" space. Right now it is using 26,906kb (or around 27mb). That's where code goes and it often has to be increased if you have many JSP pages which get compiled as well.
If you run your application with the following params you should be able to connect with jconsole to see how it's doing:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false
I suspect that you are going to see that you are using far, far less in the "Perm Gen" space. The -Xmx8192m (or -Xmx8g) is all you need typically. It will give 8gb of memory to the heap in general which is typically short lived objects. It also scales the various different memory partitions accordingly.
For more information about various heap spaces see the Java hotspot documentation.

Eclipse Juno with JRE 7 causes problems on startup

The issue that is explained seems to be a common one and different solutions have been proposed already, many of which work. One example of this discussion can be found here.
My question is more about why rather than how.
We have been wrestling with this issue here ourselves as well and found that if we launch eclipse using javaw.exe the problem occurs, but if we invoke Eclipse using jvm.dll the problem does not appear. Even though in both cases the eclipse.ini remained same.
To explain my case I will use the example of launching eclipse.exe from command line with a single -vm argument. For reference below is the eclipse.ini that we are using:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20120522-1813
--launcher.XXMaxPermSize
256m
-vmargs
-Xms128m
-Xmx1280m
-XX:MaxPermSize=512m
-Dderby.stream.error.field=java.lang.System.err
You can see that the memory requested for allocation is quite a lot for both heap (1280m) and PermGen (512m). If you are unable to reproduce the issue you can try increasing the memory until the error occurs.
There are three different command lines that you may use:
eclipse.exe -vm ..\jre\bin\javaw.exe
eclipse.exe -vm ..\jre\bin
eclipse.exe -vm ..\jre\bin\client\jvm.dll
Only the first one causes the error (javaw.exe). The remaining two options launch eclipse successfully. Reducing memory requirement in eclipse.ini also fixes the problem obviously.
So my question is, why does javaw.exe fail when the other two command lines work? What is the difference between choosing these different paths? Does one enforce parameters more strictly than the others?
Environment: Eclipse: 3.8-win32, JRE: 7u7-win32, Windows 7 x64

I can't explain why pointing Eclipse to the executable fails but the dll does not, but I can offer this to explain the problem. The gist of it is that on Windows, the JVM needs to allocate a contiguous chunk of memory for your heap, and if it can't then it fails to start.
Perhaps this page will help figure out why pointing to the dll seems to work. Otherwise, I'd ask on the Eclipse Equinox forum.

Eclipse crashing, getting heap exceptions - Out of Memory when trying to deploy an Android applicaiton

I have one Android project that crashes when it is deployed. Other projects in the same workspace work fine. I increased the RAM usage on the AVD that I'm using to 1 GB. I don't think there is a memory leak because it seems to work on other peoples computer.
I'd like to use the Memory Profiler, but the project crashes before launching, and I can't reach the Logcat files.
Right now I'm using eclipse, is there a way for me to launch it using ANT or the command line, where I can execute it step by step and find where the crash is happening?
Any help would be greatly appreciated.
Thank you,
David

david
Try to increase heap size of the eclipse in vm arguments from eclipse.ini file for example by default it will like
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
You can change something like
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms512m
-Xmx1024m
-XX:PermSize=256M
-XX:MaxPermSize=512M