Unable to execute dex: GC overhead limit exceeded in Google Play Services? - java

I am stuck in last two days and try to run the project and also i changed many values but still same error with google play services. i am using eclipse juno 64bit and using alot of APIs jar and projects google play services is one of them. This is my below file can any body help me please how to get rid of this dam problem. its waste my lot of time.
-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
com.android.ide.eclipse.adt.package.adtproduct
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=512m
-Xms512m
-Xmx1024m

Related

one app shows Unable to execute dex: GC overhead limit exceeded GC overhead limit exceeded in eclipse

I have tried to read some of the questions answered on stackoveflow and changed eclipse.ini according to this:
Now every app is running properly except one. It shows this message:
Unable to execute dex: GC overhead limit exceeded
GC overhead limit exceeded
It forces eclipse to crash. Is there any other way to fix this or is this my projects problem ?
Thanks!
locate the
eclipse.ini
file in your Eclipse's installation directory. Then Copy and past the following content :
openFile
--launcher.XXMaxPermSize
1024m
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
1024m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms512m
-Xmx1024m

Error starting eclipse exit code=13

I have already searched for this but i cant find something that answer this (tried some but i dont understand how to proceed or it just dont works)
So here am I, when I launch eclipse it just doesn't start and I got this message:
If I understood well, the eclipse.ini file has something to do with the problem. Here it is:
Sorry for my language, I am not native english so, I tried to explain as best as I could.
You have a 32bit OS and you are trying to use a 64bit eclipse and/or 64bit JDK
Before to do this i suggest to verify the type of your OS(32 or 64 bit).
-I also advise you to check the version of java and eclipse IDE that you have downloaded and installed
After this try to erase the string from your ENV path of WINDOWS from System->Advanced settings->enviroment path
and erase the string C:\ProgramData\Oracle\Java\bin;
if it doesn't work yet try to modify your eclipse.ini like this:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
**-vm
C:\Program Files\Java\jre1.8.0_31\bin\javaw.exe**
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Xmx512m
you must put the string before vmargs and put the correct release of java.
Also you have to put -vm and a new line the path

Eclipse throws "Unable to create new native thread.". How to fix it?

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.

getting failed to create java virtual machine error everytime I try to open eclipse [duplicate]

This question already has answers here:
Eclipse error: 'Failed to create the Java Virtual Machine'
(43 answers)
Closed 9 years ago.
I have tried a variety of different solutions found on stack and other places on google and I keep getting the same error message every time I try to open eclipse. It has been running fine for several years and then three days ago I shut it down. Today I tried to reopened it and I keep getting the message. Here is the code from the Eclipse.ini file. I am using a Mac version 10.6.8. Here is a screen shot. Any help would be appreciated.
-startup
../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.100.v20110502
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
It might be that Java isn't up to date. Go to Software Update on your mac and update Java. After trying everything else on other forums, this finally worked!
http://java.com/en/download/apple_manual.jsp?locale=en
Try removing the line : 256m which is after --launcher.XXMaxPermSize

Java heap space error in uploading document through webservice

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.

Categories

Resources