Develop Reference

JVM SIGSEGV crash in native without any named library

We've now encountered two times a SIGSEGV crash in Oracle 1.8.0_60 JVM where the error log doesn't even implicate any library, just says that crash happened in native code:
# Problematic frame:
# C 0x00007f6d04000000
#
and
# Problematic frame:
# C 0x00007fc6ec048ff0
#
Both times the thread that crashes is an application thread. Either a ForkJoinPool or Tomcat ajp-bio thread.
What could've gone wrong? Normally when there's a failure in native libraries, there's a name of the library included.
What I see in sanitized hs_err-logs for the first crash and the second crash (full version for comparison) doesn't give me much more ideas about what could've gone wrong as there seems to be enough memory. Just the metaspace is even near to running out.
The environment runs on 64-bit Linux:
[foo#bar ~]$ uname -a
Linux bar 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

You only posted one full log so it's not really possible to spot a pattern here, but the C frame is in a non-executable memory region and outside the code space. The VM events also show a flurry of re/deoptimizations and a bias revocation. So my guess is that might be a miscompilation.
Things you can try:
update your JVM. 8.0_60-b27 is not the latest patch level.
try -XX:-UseBiasedLocking -XX:-TieredCompilation
try -XX:-UseBiasedLocking -XX:TieredStopAtLevel=1
If updating the vm does not fix it but one of the options does then it's probably a VM bug and you should file with your linux distribution or oracle.

"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.

An internal error occurred during: "Updating indexes".Java heap space during eclipse start up?

I am getting below error while starting eclipse
An internal error occurred during: "Updating indexes".Java heap space?
It was running fine half an hour before.I restarted the eclipse and getting this error now? i have 8 gb ram,window 7 64 bit OS.
i have tried restarting my system but nothing helped?
-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
-showLocation
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vm
C:/Program Files (x86)/Java/jdk1.6.0_25/bin/javaw.exe
-vmargs
-Dfile.encoding=UTF-8
-Dosgi.requiredJavaVersion=1.5
-Xms512m
-Xmx1024m
Not sure what i is the issue?

If you have m2e or other Maven plugin installed, you should check if the option at 'Window -> Preferences -> Maven -> Download repository updates index on startup' is enabled. Disable it and see if it resolves out of memory issue.

If you are using eclipse or myeclipse, you can increase memory by making changes in .ini file (myeclipse.ini)
-Xmx2048m
-XX:MaxPermSize=1024m
-XX:ReservedCodeCacheSize=512m
-Dosgi.nls.warnings=ignore
It will solve problem connected with heap space.

Assuming this is a heap space problem, try this FAQ:
Eclipse-Wiki: FAQ How do I increase the heap size available to Eclipse?

This may not be directly related to the question, but this fixed the java heap issues I had:
Launch eclipse using eclipse -vmargs -Xmx2048m.
From the readme included with the eclipse install:
By default, Eclipse will allocate up to 512 megabytes of Java heap
memory. This should be ample for all typical development tasks.
However, depending on the JRE that you are running, the number of
additional plug-ins you are using, and the number of files you will be
working with, you could conceivably have to increase this amount.
Eclipse allows you to pass arguments directly to the Java VM using the
-vmargs command line argument, which must follow all other Eclipse specific arguments. Thus, to increase the available heap memory, you
would typically use:
eclipse -vmargs -Xmx<memory size>
with the value set to greater than "512M" (512 megabytes
-- the default).

Old question, but I got this issue and adding more memory did not solve, so I rebuilt the java index by applying this comment from eclipse bug tracker:
I Quote:
Click in "Quick Access", Type "Rebuild Java Index" (Actually just start typing it, use the auto completion), Hit enter.

Eclipse 4.2.0 / debugger very slow

After switching to Eclipse 4.2.0 the debugger seems to be not responable or very very slow. My used Java version is (same as used in Eclipse):
johannes#luna:~/sirix$ java -version
java version "1.7.0_03"
OpenJDK Runtime Environment (IcedTea7 2.1.1pre) (7~u3-2.1.1~pre1-1ubuntu3)
OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)`
Anyone else encountered the same behavior?
Edit: I have had too many (old) breakpoints (maybe especially breakpoints on checked and unchecked exceptions are especially costly ;-))

I don't know about how to speed up the debugging in Eclipse, but there are some general rules you can follow to speed up Eclipse on a whole:
Disable antivirus software, or add your JDK & eclipse & workspace & other related folder to white list in your antivirus software.
Disable unnecessary validations and startup action in Eclipse reference.
For validations: on Eclipse menu Windows -> Preferences -> Validation, click “Disable All”, and then select the validator which you need. I selected “Classpath Dependency Validator” only.
For startup action: on eclipse menu Windows -> Preferences, type “startup”, select “Startup and Shutdown”, untick the options you don’t need. (Thanks for David’s suggest, I’ve added the above 2 detail steps for readers)
Modify eclipse.ini to set the Xmn(new generation size), Xms and Xmx, enable parallel GC
-vm C:/jdk1.6.0_25/bin
-startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
–launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502
-product org.eclipse.epp.package.jee.product
–launcher.defaultAction openFile
–launcher.XXMaxPermSize 256M
-showsplash org.eclipse.platform
–launcher.XXMaxPermSize 256m
–launcher.defaultAction openFile
-vmargs
-server
-Dosgi.requiredJavaVersion=1.5
-Xmn128m
-Xms1024m
-Xmx1024m
-Xss2m
-XX:PermSize=128m
-XX:MaxPermSize=128m
-XX:+UseParallelGC
Create a ram disk(virtual disk) on memory, and put your jdk on the ram disk.
You can use imdisk to create ram disk. Firstly download it from: http://www.ltr-data.se/opencode.html/#ImDisk, and install it.
Then set the ImDisk driver to auto-load at Command Prompt with administrative privileges (for example right-click, start as Administrator), type:
sc config imdisk start= auto
net start imdisk
Create a 200m ram disk as driver n by:
imdisk -a -t vm -s 300m -m n:
Then you should format the ram disk manually.
Later, if you would like to remove the ram disk, just run the command:
imdisk -D -m n:
Make sure you are using Sun JDK, not open JDK/GCJ nor other JDK on Linux.
If you are not satisfied with the after the above steps, install jRockit instead of Sun JDK, and change some of the VM options by jRocket specification,
jRockit is faster than Sun JDK.

Check that you don't have any method breakpoints. Those can be incredibly slow.

Make sure you clear all the expression in the Expression window when debugging. Add expressions only when u require and remove after use.

Java - OutOfMemoryError: PermGen space

I'm currently developing a tool allowing me to get statistics from anyware simply by going on a website I also created.
For those who don't know, Birt is a reporting tool, and an eclipse plugin.
My problem is the following :
I installed tomcat on the server hosting my website, and installed the Birt ReportEngine on it, and on my website, I call the online viewer to get my reports.
The problem is that since yesterday, when I launch a report, I have this error :
javax.servlet.ServletException: L'exécution de la servlet a lancé une exception
org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
Caused by :
java.lang.OutOfMemoryError: PermGen space
I don't really know which config file to modify to avoid this error. I found some examples online that tell to modify the eclipse.ini file, but as for mty website, I don't use eclipse, I didn't found any usefull post.
Can someone help me please ?
Thanks

As said by Thomas, the parameter to set is -XX:MaxPermSize. One way of setting this parameter for Tomcat is to use the CATALINA_OPTS environment variable.
For Windows :
set CATALINA_OPTS=-Xms512m -Xmx512m -XX:MaxPermSize=256m
For Linux (bash) :
export CATALINA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=256m"
Check the startup.bat and catalina.bat or startup.sh and catalina.sh files in your tomcat/bin directory and add the above commands there.
(The Xmx and Xms parameters set the minimum and maximum size for the Java heap - where objects are stored. This is not the problem you have but I included them for the sake of completeness.)

You need no add the following line to eclipse.ini
-XX:MaxPermSize=128m
If the problem occurs again try to increase the value. You can also add the following optional lines:
-XX:+UseConcMarkSweepGC
-XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled
-XX:+UseParNewGC
This changes the Garbage Collector of the JVM to a more optimized one, and can also improve the performance and memory usage.
You may also want to tweak the values of the -Xmx and Xms options. Try small increases (same to the -XX:MaxPermSize) as this will increase the memory footprint of your JVM.
For a more explained details see here:
http://www.eclipsezone.com/eclipse/forums/t61618.html
For a complete list of the JVM parameters and options:
http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html

Use that JVM option: -XX:MaxPermSize=256m (of course you are free to choose the amount of memory, but IIRC the default would be 64m so you'd need to increase that). - Note that this is for Oracle's JVM (formerly SUN's :) ) , other JVM's might have different options.
Other than that, try not hot deploying too much, since that might also increase the PermGen space usage (JBoss which includes Tomcat as has that problem, but I'm not sure whether that is true for a standalone Tomcat).

This can be solved by allocating more heap memory.
this can be done as:
steps:
double click on your eclipse server->open launch configuration->Arguments->paste this line in vm arguments text area:-
-XX:MaxPermSize=512M -Xmx1024M
This will solve your outofmemory error.

I added the below line line to eclipse.ini and working fine for me.
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256m
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m