I have a problem with Eclipse configuration and very often it throws me a message "Unable to create new native thread." and I'm prompted to restart Eclipse. I saw that there are many topics about this, but i did find anything to help me to solve my problem.
I use:
Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 2
Build id: 20130225-0426
Windows 7 Ultimate
Processor: Intel Core(TM) 2 Duo CPU T5870 # 2.20 GHz
Memory (RAM): 4.00 GB
System Type: 64-bit Operating System
My 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_1.1.200.v20120913-144807
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
F:/Oracle/Middleware/jdk160_29/bin/javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-server
-XX:PermSize=256m
-XX:MaxPermSize=256m
-Xss2m
-Xms1G
-Xmx1G
-XX:MaxGCPauseMillis=10
Can you try to adjust the Xss parameter? It controls how big the stack of each thread is, and with Xmx set to 1G giving 2 Mb for the stack of each thread seems too much for IDE threads in most cases.
Since you have 4G of RAM try changing:
-Xss2m
-Xms1G
-Xmx1G
with
-Xss512k
-Xms1G
-Xmx1512m
This should solve your issue or at least mitigate it a lot.
I also had trouble with Eclipse Luna on Fedora 20. I've read a lot about different memory options and still couldn't figure out the problem. It drove me crazy.
Finally I realized that by default, the number of processes a regular user can have on Fedora is very limited. Content of limits.d/90-nproc.conf:
* soft nproc 1000
Raising this to 5000 fixed my "Unable to create new native thread" problems.
Related
Can someone help me out with this. I just simply cannot get the VM to increase beyond 1.8GB or some reason. This utility returns 64 and 1883242496 when run in Eclipse but returns the correct values when run from the command line (java.exe). The VM is 64 bits so should go past 1.8 GB.
public static void main(String[] args) {
System.out.println(System.getProperty("sun.arch.data.model"));
System.out.println(java.lang.Runtime.getRuntime().maxMemory());
}
Eclipse.ini contents below. Tried just about everything.
-startup
plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512M
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vm
C:\Program Files\Java\jdk1.8.0_66\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms6144m
-Xmx6144m
-d64
Thanks in advance
The configuration in eclipse.ini sets the memory used by Eclipse itself, it does not change the memory used when you run a program from within Eclipse.
You can change the setting for a particular program by opening 'Run > Run Configurations' and selecting your program in the 'Java Applications' section and add your arguments to the 'VM arguments'.
You can also set the default as shown in another answer.
Even by setting both to same heap size 6144m
-Dosgi.requiredJavaVersion=1.7
-Xmx6144m
-Xmx6144m
in eclipse.ini is not increasing the heap size for 64 sit but by passing argument for JVM using windows--> preference we can increase the heap size
You can try this:
-startup
plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
6144m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms6144m
-Xmx6144m
-XX:+UseParallelGC
-XX:PermSize=6144M
-XX:MaxPermSize=6144M
-d64
Hope it will help.
I recently had a problem with loading projects in an eclipse program.
The error was related to garbage collection (GC).
When searching for a solution online, I noticed this is due to the memory allocation.
In Eclipse, as you may know, the ini file could be used to allocate minimum and maximum memory allocated to the program.
-Xms Initial memory size
-Xmx maximum memory size
When the value of –Xmx was changed to higher value 2048m, I expected the program to load all the projects without any problem.
But, I could see the same error.
When I looked into little further, there was a system variable _JAVA_OPTIONS with value -Xmx512M. This had overwritten the values in the ini file.
Reflection:
It is worth to also look into the system variables when the program does not reflect the values in the ini files.
I m using Eclipse Indigo. It becomes unresponsive often and finally prompts saying out of memory error and asks me to exit workbench. I increased the Perm Gen space as told in one of the eclipse forums by editing my eclipse.ini file.
Eclipse.ini file contents now is as below,
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_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
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-vm C:/Java/jdk1.5.0_15
I mostly do Javascript development in eclipse. And I am not able to edit JS file in eclipse.
What can I do to solve this problem?
Currently maximum only 512MB is allowed for eclipse in your ini (-Xmx512m), if you have enough RAM you shall try increasing it to 1GB. More info here http://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_available_to_Eclipse%3F
This problem may be due to
You are using old java version , You need to upgrade it with new version
If your operation system is 64 bit make sure that you are using 64bit java
Java 5 is pretty old. The GC (and overall optimizations) are slow, outdated and patch level 15 means you're missing many critical bug fixes.
The first step would be to install Java 7 (lastest version). Make sure you disable the browser plugin because of the security risks.
Then make sure that Eclipse uses it: Update the path after -vm. Note: If your path contains spaces, use this:
-vm
c:\Program Files\Java\...
(i.e. put the path into a line of it's own).
Lastly, there are two kinds of memory in Java. Heap and PermGen. The error message tells you which one ran out. Use -Xmx to set heap memory and -XX:MaxPermSize= for PermGen. 256m PermGen should be enough but some script languages need more.
With Java 7, enable GC1 which should give you better performance: -XX:+UseG1GC
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.
HI
I am uploading the documents through webservice into the server.. when i am uploading the <10MB file, it is working fine & it is >10MB it is thrown the following error in the console..
I had the using the following parameters in the eclipse..
-startup
plugins/org.
clipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
--256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
--512m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms128m
-Xmx384m
-Xss4m
-XX:PermSize=300m
-XX:MaxPermSize=300m
-XX:CompileThreshold=5
-XX:MaxGCPauseMillis=10
-XX:MaxHeapFreeRatio=70
-XX:+CMSIncrementalPacing
-XX:+UnlockExperimentalVMOptions
-XX:+UseG1GC
-XX:+UseFastAccessorMethods
I am getting error as
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
The file was uploading the server with 0KB..
Any one can help me resolve this issue
Thanks,
Murali
Why are you allocating so much PermGen space (--launcher.XXMaxPermSize --512m and -XX:PermSize=300m and -XX:MaxPermSize=300m)? Virtually nothing needs that much PermGen space. Most applications don't need more than 128M. If you have a server for a complex application that's meant to run forever then you may be justified in increasing the value to 256M. But 512M is unnecessary.
I would suggest reducing these three options to 256M (or even 128M), and then replacing -Xmx384m with -Xmx512m and seeing if that resolves the issue.
My settings for these values in eclipse.ini are:
-Xms768M
-Xmx1024M
When setting them higher, Eclipse doesn't start anymore. Is there a way to increase these values without Eclipse crashing?
The maximum values do not depend on Eclipse, it depends on your OS (and obviously on the physical memory available).
You may want to take a look at this question: Max amount of memory per java process in Windows?
I am guessing you are using a 32 bit eclipse with 32 bit JVM. It wont allow heapsize above what you have specified.
Using a 64-bit Eclipse with a 64-bit JVM helps you to start up eclipse with much larger memory. (I am starting with -Xms1024m -Xmx4000m)
Why do you need -Xms768 (small heap must be at least 768...)?
That means any java process (search in eclipse) will start with 768m memory allocated, doesn't that? That is why your eclipse isn't able to start properly.
Try -Xms16 -Xmx2048m, for instance.
I have tried the following config for eclipse.ini:
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
1024M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
1024m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms128m
-Xmx2048m
Now eclipse performance is about 2 times faster then before.
You can also find a good help ref here: http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html