Android java.exe finished with non-zero exit value 1

Question

I've tried looking at similar ones and no solution has worked. I've previously run apps without a problem but my new app suddenly started giving me problems. It always fails when I try to run it saying:

Error:Execution failed for task ':app:preDexDebug'.
com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files (x86)\Java\jdk1.7.0_67\bin\java.exe'' finished with non-zero exit value 1

Here is what the console displayed:

Executing tasks: [:app:assembleDebug]

Configuration on demand is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:compileDebugNdk UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportSupportV42200Library UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:compileDebugJava UP-TO-DATE
:app:preDexDebug
AGPBI: {"kind":"SIMPLE","text":"Error: Could not create the Java Virtual        Machine.","position":{},"original":"Error: Could not create the Java Virtual Machine."}
AGPBI: {"kind":"SIMPLE","text":"Error: A fatal exception has occurred. Program will exit.","position":{},"original":"Error: A fatal exception has occurred. Program will exit."}

AGPBI: {"kind":"SIMPLE","text":"Error: Could not create the Java Virtual Machine.","position":{},"original":"Error: Could not create the Java Virtual Machine."}
AGPBI: {"kind":"SIMPLE","text":"Error: A fatal exception has occurred. Program will exit.","position":{},"original":"Error: A fatal exception has occurred. Program will exit."}


FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:preDexDebug'.
com.android.ide.common.process.ProcessException:     org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files (x86)\Java\jdk1.7.0_67\bin\java.exe'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2.614 secs

AGPBI: {"kind":"SIMPLE","text":"Error: Could not create the Java Virtual Machine.","position":{},"original":"Error: Could not create the Java Virtual Machine."}
AGPBI: {"kind":"SIMPLE","text":"Error: A fatal exception has occurred. Program will exit.","position":{},"original":"Error: A fatal exception has occurred. Program will exit."}

This app is very simple and I have not changed it much from the stock layout. It is designed only for lollipop and uses only stock features. Here is the build.gradle:

apply plugin: 'com.android.application'
android {
compileSdkVersion 22
buildToolsVersion "22.0.0"

defaultConfig {
    applicationId "com.package.app"
    minSdkVersion 21
    targetSdkVersion 22
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}
}

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:support-v4:22.0.0'
}

Note that this is a problem with *building* your app, not with running it - though of course you have to managed to build successfully at some point before you can run it. — Chris Stratton, Mar 24 '15 at 15:14
@Rand, did you find any solution ? I am facing the same issue, I have 32 bit configuration, I guess this is the issue. — Narendrasinh Dodiya, Jun 27 '15 at 05:11
Search your layout.xml and find `android:shadowRadius="4dp" ` and delete it. — meyasir, Nov 15 '18 at 10:28

score 56 · Answer 1 · answered Apr 05 '15 at 16:11

56

Had the same error encountered which was due to conflicting drawable resources. I did a clean project and the error was no longer encountered.

answered Apr 05 '15 at 16:11

Kenneth

577
1
3
2

this worked for me. i had exit error 2 – hadi Oct 05 '15 at 07:57
1

Wh00t, so simple! I had exit error 1.. Must have been some mixup between the team via git – Sindri Þór Jan 17 '16 at 21:29
Like SindriÞór I also had exit error 1 and this has solved it for me. Last hour was nothing but headaches, thanks @Kennth ! – davewoodhall Feb 06 '16 at 00:14
1

@Kenneth not working..! – user5716019 Mar 01 '16 at 05:20
this not works for me – jose920405 Jul 12 '17 at 13:59

score 16 · Answer 2 · edited Aug 24 '17 at 17:14

16

After a lot of surfing, i found out the problem is GC overhead (out of memory). By adding below code to my build.gradle saved my day.

android {

    dexOptions {
        incremental = true;
        preDexLibraries = false
        javaMaxHeapSize "4g" // 2g should be also OK
    }

}

reference - ProcessException: org.gradle.process.internal.ExecException finished with non-zero exit value 2

edited Aug 24 '17 at 17:14

sharkbyte

33
7

answered Dec 18 '15 at 12:14

Duke1992

185
1
13

What's `g`? Gigabyte? – Subby Jul 08 '16 at 14:38
@Subby It is just an option to specify the maximum memory allocation pool for a Java Virtual Machine (JVM) for dex operation. ref - http://stackoverflow.com/questions/33750404/android-gradle-what-is-javamaxheapsize-4g – Duke1992 Jul 13 '16 at 08:35
2

`DexOptions.incremental` is obsolete and will be removed at the end of 2018 – HendraWD Sep 12 '18 at 12:02

score 13 · Accepted Answer · edited Feb 12 '16 at 15:39

13

It must have been a problem with my Java install. I removed all traces of Java (C://program files/Java/jdk) and jre folders and reinstalled it from the official page and now it works fine.

edited Feb 12 '16 at 15:39

bendaf

2,981
5
27
62

answered Mar 29 '15 at 15:59

Rand

1,653
2
12
15

1

How did you did that. Please provide more details – Sami Eltamawy Apr 13 '15 at 14:53
1

Go into the control panel and uninstall all versions of Java. Then reinstall the latest one. – Rand Apr 14 '15 at 20:16
1

didn't work for me.. – Alex K Apr 24 '15 at 14:26
You can try "JavaRa" to remove traces of Java. Not sure if it helps though. – android developer Aug 11 '15 at 21:36
In case you have multiple JDK's installed (for whatever reason), make sure studio is using the right one: http://stackoverflow.com/a/30631386/1544046 – JCricket Jul 14 '16 at 12:57

Shaun · Answer 4 · 2016-07-15T02:42:06.427

Maybe you can change your buildToolsVersion num.

this is my problem：

Error:Execution failed for task ':app:transformClassesWithDexForDebug'.
> com.android.build.api.transform.TransformException: java.lang.RuntimeException: com.android.ide.common.process.ProcessException: java.util.concurrent.ExecutionException: com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'D:\ProgramTools\Java\jdk1.7.0_79\bin\java.exe'' finished with non-zero exit value 1

my build.gradle:

android {
    compileSdkVersion 23
    buildToolsVersion "24.0.0"

    defaultConfig {
        applicationId "com.pioneers.recyclerviewitemanimation"
        minSdkVersion 15
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

I just change buildToolsVersion to buildToolsVersion "23.0.2" and the problem was solved.

That was my solution too, i just check an old project and compared build.gradle and set to the same value of buildToolsVersion "23.0.1" — Youri, Jul 18 '16 at 09:37
worked for me.... :-) problem was when i created new project. — Rumit Patel, Oct 08 '16 at 06:16

Kiryl Bielašeŭski · Answer 5 · 2017-08-02T12:22:26.267

12

Problem RAM. I had similar message in my Messages Gradle Build

Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal. 
ExecException: Process 'command 'C:\Program Files\Java\jdk1.8.0_45\bin\java.exe'' 
finished with non-zero exit value 1

Why: I didn't have free RAM on my laptop with the OS windows 8.1.

Solution: I closed a few programs that I don't need. After that, I had more free RAM and my project was built in android studio.

edited Aug 02 '17 at 12:22

answered May 02 '15 at 15:06

Kiryl Bielašeŭski

2,663
2
28
40

1

yeah, before error it show a dialog " not enough momory... " i don't remember extract message – vuhung3990 Jul 20 '15 at 14:42

score 8 · Answer 6 · edited Jun 25 '15 at 17:15

8

In my case, the solution was to close Android Studio and kill the java processs, which was very big (1.2 GB). After this, my project runs normally (OS X Mount Lion, Android Studio 1.2.2, iMac Mid 2011 4GB Ram).

edited Jun 25 '15 at 17:15

Mike Cluck

31,869
13
80
91

answered Jun 25 '15 at 16:57

Misael Barreto

81
1
2

Hadn't even thought of this. Worked for me. Simply restarting AS (like 4 times) did nothing. – gatlingxyz Jul 07 '15 at 15:09
Thanks! It worked like a charm. – jackcar Jul 31 '15 at 14:40
Mac crashed my login (not a full reboot). On logging back in, all running apps restarted putting the Java process in some weird zombie state (my best guess). Killing the Java process in activity manager fixed the issue. Thanks! – andymeadows Jan 04 '16 at 07:55
Thanks! Solution is to close Android Studio. – pengguang001 Jul 12 '16 at 08:03

score 7 · Answer 7 · answered May 31 '16 at 09:46

7

Solution

1.Just clean the project and check its working or not

2.Just Restart android studio after closing all the rubbish tasks

3.If both the above things not working add this in gradle.build file

android {

    dexOptions {
        incremental = true;
        preDexLibraries = false
        javaMaxHeapSize "4g" 
    }

}

answered May 31 '16 at 09:46

SHINTO JOSEPH

377
4
17

nice and 3 one working. – Surendar D Jul 21 '18 at 06:41

score 7 · Answer 8 · answered Feb 08 '18 at 20:06

7

Use the option assembleandroidtest as in the image below. So you can find out more about the error occurred:

answered Feb 08 '18 at 20:06

Iman Marashi

5,593
38
51

Nice solution!!! to find out exact problem!!! – Ranjithkumar Apr 27 '19 at 06:48
Thanks , Its perfect – Prinkal Kumar May 13 '19 at 10:53
Thank u man. This saved our day. Also Pelin say thank you too. – b.erdi Oct 22 '20 at 11:43

score 6 · Answer 9 · answered Apr 06 '15 at 17:43

6

I had the same issue after adding the library icepick to my gradle dependencies. After removing the dependencie, everything seems to be fine. As soon as i know why this issue appeared i'll write here again

answered Apr 06 '15 at 17:43

0xPixelfrost

10,244
5
39
58

4

Same here. The fix was to use `provided` instead of `compile` for the `processor` dependency. See [this ticket](https://github.com/frankiesardo/icepick/issues/46). – theblang May 13 '15 at 03:20

score 3 · Answer 10 · answered Jul 06 '15 at 05:17

3

After adding a jar file to a project's lib folder and after adding it to the build.gradle file as compile'path example' when you sync the gradle it add an additional line as compile files('libs/example.jar'). You just need to remove the line you previously added to the build.gradle file i.e. the compile'path example' after the gradle sync. You also need to remove the line compile fileTree(dir: 'libs', include: '*.jar')

answered Jul 06 '15 at 05:17

Tony Stark

451
1
3
11

In your case just remove the line compile fileTree(dir: 'libs', include: ['*.jar']). Hope it will work fine for you. – Tony Stark Jul 06 '15 at 05:20
This worked for me as well. I do not know why this is so difficult for me iOS adding dependencies and managing these is wayyyy more simple. – JMStudios.jrichardson Sep 17 '15 at 16:49

score 3 · Answer 11 · answered Jul 31 '15 at 15:38

3

compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_7
        targetCompatibility JavaVersion.VERSION_1_7
    }

add this to your gradle Build. It worked for me

answered Jul 31 '15 at 15:38

Ashok Varma

3,489
3
28
43

2

that doesn't work for me – letsdev-cwack Nov 24 '15 at 12:31
@letsdev-cwack did you have same problem ?? – Ashok Varma Nov 24 '15 at 13:16

Fabio de Toledo · Answer 12 · 2015-08-18T18:13:22.477

3

The answer for me was to free memory to the build process, closing programing or rebooting the machine (win10 seems to manage memory worse than win7)

Why did it fixed for me?

During the build, android studio doesn't find enough memory to compile but it doesnt show any error. The :app:preDexDebug error happened just when I tried to upload the compiled app to the phone.

Sometimes I could get through this point (no app:preDexDebug error), but when running the application on android I got "ClassNotFound" exceptions. This was the clue to discover android studio wasn't compiling all my files during build because of the lack of memory (win10 asked me to close android studio to save memory during the build), even though the IDE showing me that the build was successful.

edited Aug 18 '15 at 18:13

answered Aug 18 '15 at 13:43

Fabio de Toledo

153
1
7

This more like question about the exceptions or a comment rather than an answer. If this is an answer please mention how you fixed all the exceptions you are mentioning about, if this is a new question ask a new question about the previously you are getting. – Ram Aug 18 '15 at 14:07
Thank you for the feedback, Tried to make myself clear. I dont master English, but I spent some hours in this problem that i decided to post what worked for me. ;-) – Fabio de Toledo Aug 18 '15 at 18:18

score 3 · Answer 13 · edited May 23 '17 at 11:33

3

Cleaning and rebuilding the project works for me. In Android studio:

Build -> Clean Project 
Build -> Rebuild Project

Refer link

edited May 23 '17 at 11:33

Community

1
1

answered Jan 04 '16 at 09:57

huu duy

2,049
21
31

2

it doesn't work for me :( – Kairi San Jan 20 '16 at 04:52

score 1 · Answer 14 · answered Mar 27 '15 at 16:18

1

I have tried virtually everything until I tried to run the script from error in command line:

dx.bat -JXmx1536m --dex --output \build\intermediates\pre-dexed\debug\classes-01b5c6cd66151f573da9773c18af55d10736a24e.jar build\intermediates\exploded-aar\aaa-release\classes.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Then I commented out developer's memory setting in gradle script:

//        javaMaxHeapSize "1536m"

and I was able to pass this error. I need to increase RAM in my laptop.

answered Mar 27 '15 at 16:18

Leos Literak

8,805
19
81
156

how did you set javaMaxHeapSize? I set it using gradle.properties, but it only works for gradle daemon. – Sarowar Jun 10 '15 at 09:54
1

javaMaxHeapSize is a property under `android.dexOptions`. I had it at 3gb myself at a Win10 install with 16GB ram. Decreasing it to 1 or removing it fixed it (ironically) for me – Nilzor Dec 15 '15 at 18:02
Yes, also strangely enough decreasing it to 1gb in my project from 3gb worked. I have plenty of RAM so very strange. – zaifrun Apr 26 '16 at 09:10

score 1 · Answer 15 · answered Jun 01 '15 at 06:53

1

You must update all blocks in SDK Manager (Support Library, etc.), all non updated libs and packages. After this you must sync gradle files with project and rejoice!

answered Jun 01 '15 at 06:53

Алешин Михаил

13
2

Shahidul · Answer 16 · 2016-01-29T08:21:09.150

1

In my case setting Java Max Heap Size from 2g to 1g worked.

Add following to application module's build.gradle file

android {
    dexOptions {
        javaMaxHeapSize "1g"
    }
}

edited Jan 29 '16 at 08:21

answered Jan 29 '16 at 04:56

Shahidul

2,997
1
21
20

score 1 · Answer 17 · answered Apr 13 '17 at 07:20

This solution work for me

Install Java JDK 8.

Then, go to Tools-> Options ->Tools for Apache Cordova-> Environment Variable Overrides and set the path to your JDK to "C:\Program Files\java\jdk1.8.0_121" to get Java 8 instead of Java 7.

for more info http://www.developersite.org/103-141954-android

Yvgen · Answer 18 · 2017-11-09T21:47:46.193

1

Experimental I found way:

App extends Application not MultiDexApplication

and remove

org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

from gradle.properties

edited Nov 09 '17 at 21:47

answered Nov 09 '17 at 21:18

Yvgen

2,036
2
23
27

score 0 · Answer 19 · answered May 21 '15 at 05:16

0

I got this error after transferring my project from my laptop to my desktop in Android Studio.

My solution was to restart Android Studio, then clean the project and finally execute the project.

answered May 21 '15 at 05:16

BhavikUp

105
1
2

Adri Stanchev · Answer 20 · 2015-07-18T05:36:35.943

0

I had the same issue, after trying each of the answers here, I noticed that a package which I had renamed had not been renamed in a class which imported it. I fixed the name and immediately solved the problem.

edited Jul 18 '15 at 05:36

answered Jul 17 '15 at 12:35

Adri Stanchev

1
3

score 0 · Answer 21 · answered Jul 30 '15 at 23:16

0

This is likely due to your app exceeding the 65k method count, thus causing a dex error. There is no solution, other than enabling multidexing in your app.

answered Jul 30 '15 at 23:16

IgorGanapolsky

26,189
23
116
147

score 0 · Answer 22 · answered Aug 27 '15 at 00:57

Well there can be many problems associated with it. First of all check whether you messed up with some file placements. for example what I did is I placed non xml file in anim folder, which isn't allowed. So check whether such things happened to you as well.

score 0 · Answer 23 · answered Sep 11 '15 at 10:24

Have you enabled multidexing?. Do extend your main Application class with MultiDexApplication. I have got additional exception mesage before the error. They are as follows.

Uncaught translation error: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded

Uncaught translation error: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
2 errors; aborting

This clearly tells that the error occurred due to out of memory. Try the following:

extend your main Application class with MultiDexApplication.
close unused applications from background and restart Android Studio.

This will do the trick ;)

score 0 · Answer 24 · answered Oct 24 '15 at 07:29

0

Give this mother a chance:

 dependencies {
        classpath 'com.android.tools.build:gradle:1.4.0-beta6'
    }

Don't forget to bookmark this.

answered Oct 24 '15 at 07:29

Martin Pfeffer

12,471
9
59
68

score 0 · Answer 25 · answered Dec 13 '15 at 11:05

I've had the same issue just now, and it turned out to be caused by a faulty attrs.xml file in one of my modules. The file initially had two stylable attributes for one of my custom views, but I had deleted one when it turned out I no longer needed it. This was apparently, however, not registered correctly with the IDE and so the build failed when it couldn't find the attribute.

The solution for me was to re-add the attribute, run a clean project after which the build succeeded and I could succesfully remove the attribute again without any further problems.

Hope this helps someone.

score 0 · Answer 26 · answered Feb 22 '16 at 14:18

There's many reason that leads to

com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.8.0_60\bin\java.exe'' finished with non-zero exit value 1

If you are not hitting the dex limit but you are getting error similar to this Error:com.android.dx.cf.iface.ParseException: name already added: string{"a"}

Try disable proguard, if it manage to compile without issue then you will need to figure out which library caused it and add it to proguard-rules.pro file

In my case this issue occur when I updated compile 'com.google.android.gms:play-services-ads:8.3.0' to compile 'com.google.android.gms:play-services-ads:8.4.0'

One of the workaround is I added this to proguard-rules.pro file

## Google AdMob specific rules ##
## https://developers.google.com/admob/android/quick-start ##

-keep public class com.google.ads.** {
   public *;
}

score 0 · Answer 27 · answered Apr 20 '16 at 04:14

I resolve this problem with a joking way. I have two class with names startDl and StartDl. I just change one of them to StartDownload and my problem solved. also can resources have a name that already is reserved with anymore resource in project. just rename similar names to different.

score -1 · Answer 28 · edited Nov 10 '15 at 13:56

-1

All you need to do is to kill some of the running process and free the space on your Memory(RAM). You can try closing some of the high memory consuming program. You can also try restarting the Android Studio. It worked for me.

edited Nov 10 '15 at 13:56

Thomas R.

7,988
3
30
39

answered Nov 10 '15 at 10:44

vikky

77
9

score -2 · Answer 29 · edited May 29 '16 at 21:38

-2

Remove the line:

('com.android.support:support-v4:22.0.0')

From dependencies (in build.gradle):

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:support-v4:22.0.0'
}

edited May 29 '16 at 21:38

Tomasz Dzieniak

2,765
3
24
42

answered Mar 24 '15 at 15:06

Shehroz Saleem

196
2
15

13

And why do you think it would work, please explain so we understand – Aman Alam Sep 02 '15 at 11:37

score -2 · Answer 30 · edited Oct 19 '16 at 15:10

-2

For me this works:

defaultConfig {
    multiDexEnabled true
}

edited Oct 19 '16 at 15:10

Eugen Pechanec

37,669
7
103
124

answered Oct 18 '16 at 06:12

Ali Akram

199
4
12

Android java.exe finished with non-zero exit value 1

30 Answers30

Linked

Related