android studio 0.4.2: Gradle project sync failed error

Question

After updating to 0.4.2 I get this error when opening a project: 'Gradle project sync failed. Basic functionality (e.g. editing, debugging) will not work proprerly'

The event log shows this:

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.

    at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:109)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:90)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:95)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:72)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:149)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:74)
    at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:42)
    at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:29)
    at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:53)
    at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:30)
    at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:106)
    at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:100)
    at org.gradle.tooling.internal.provider.DefaultConnection.run(DefaultConnection.java:143)
    at org.gradle.tooling.internal.consumer.connection.ActionAwareConsumerConnection.run(ActionAwareConsumerConnection.java:40)
    at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter$1.run(DefaultBuildActionExecuter.java:53)
    at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:82)
    at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58)
    at org.gradle.tooling.internal.consumer.connection.LoggingInitializerConsumerActionExecutor.run(LoggingInitializerConsumerActionExecutor.java:44)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55)
    at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
2014-01-12 02:57:48,886 [  33025]   INFO - .BaseProjectImportErrorHandler - Failed to import Gradle project at 'C:/android/workspace_studio/Noggle' 
org.gradle.tooling.GradleConnectionException: Could not run build action using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.9-all.zip'.
    at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:55)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:57)
    at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
    at org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
    at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter.run(DefaultBuildActionExecuter.java:43)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.doResolveProjectInfo(GradleProjectResolver.java:170)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.access$000(GradleProjectResolver.java:61)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$1.fun(GradleProjectResolver.java:117)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$1.fun(GradleProjectResolver.java:113)
    at org.jetbrains.plugins.gradle.service.project.GradleExecutionHelper.execute(GradleExecutionHelper.java:182)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:113)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:61)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:41)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:37)
    at com.intellij.openapi.externalSystem.service.remote.AbstractRemoteExternalSystemService.execute(AbstractRemoteExternalSystemService.java:59)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl.resolveProjectInfo(RemoteExternalSystemProjectResolverImpl.java:37)
    at com.intellij.openapi.externalSystem.service.remote.wrapper.ExternalSystemProjectResolverWrapper.resolveProjectInfo(ExternalSystemProjectResolverWrapper.java:49)
    at com.intellij.openapi.externalSystem.service.internal.ExternalSystemResolveProjectTask.doExecute(ExternalSystemResolveProjectTask.java:48)
    at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:137)
    at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:123)
    at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$3.execute(ExternalSystemUtil.java:471)
    at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$4$2.run(ExternalSystemUtil.java:549)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:464)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:178)
    at com.intellij.openapi.progress.ProgressManager.executeProcessUnderProgress(ProgressManager.java:209)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:212)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:171)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$8.run(ProgressManagerImpl.java:373)
    at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:436)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:153)
Caused by: org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.9/userguide/gradle_daemon.html
Please read below process output to find out more:
-----------------------
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.

    at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:109)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:90)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:95)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:72)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:149)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:74)
    at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:42)
    at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:29)
    at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:53)
    at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:30)
    at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:106)
    at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:100)
    at org.gradle.tooling.internal.provider.DefaultConnection.run(DefaultConnection.java:143)
    at org.gradle.tooling.internal.consumer.connection.ActionAwareConsumerConnection.run(ActionAwareConsumerConnection.java:40)
    at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter$1.run(DefaultBuildActionExecuter.java:53)
    at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:82)
    at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58)
    at org.gradle.tooling.internal.consumer.connection.LoggingInitializerConsumerActionExecutor.run(LoggingInitializerConsumerActionExecutor.java:44)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55)
    at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
2014-01-12 02:57:48,893 [  33032]   WARN - nal.AbstractExternalSystemTask - A fatal exception has occurred. Program will exit.

com.intellij.openapi.externalSystem.model.ExternalSystemException: A fatal exception has occurred. Program will exit.

    at org.jetbrains.plugins.gradle.service.project.GradleExecutionHelper.execute(GradleExecutionHelper.java:185)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:113)
    at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:61)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:41)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl$1.produce(RemoteExternalSystemProjectResolverImpl.java:37)
    at com.intellij.openapi.externalSystem.service.remote.AbstractRemoteExternalSystemService.execute(AbstractRemoteExternalSystemService.java:59)
    at com.intellij.openapi.externalSystem.service.remote.RemoteExternalSystemProjectResolverImpl.resolveProjectInfo(RemoteExternalSystemProjectResolverImpl.java:37)
    at com.intellij.openapi.externalSystem.service.remote.wrapper.ExternalSystemProjectResolverWrapper.resolveProjectInfo(ExternalSystemProjectResolverWrapper.java:49)
    at com.intellij.openapi.externalSystem.service.internal.ExternalSystemResolveProjectTask.doExecute(ExternalSystemResolveProjectTask.java:48)
    at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:137)
    at com.intellij.openapi.externalSystem.service.internal.AbstractExternalSystemTask.execute(AbstractExternalSystemTask.java:123)
    at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$3.execute(ExternalSystemUtil.java:471)
    at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$4$2.run(ExternalSystemUtil.java:549)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:464)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:178)
    at com.intellij.openapi.progress.ProgressManager.executeProcessUnderProgress(ProgressManager.java:209)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:212)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:171)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl$8.run(ProgressManagerImpl.java:373)
    at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:436)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:153)

2014-01-12 02:57:48,895 [  33034]   WARN - .project.GradleProjectImporter -  
2014-01-12 02:57:48,895 [  33034]   INFO - .project.GradleProjectImporter - A fatal exception has occurred. Program will exit.


Consult IDE log for more details (Help | Show Log) 
2014-01-12 02:57:48,941 [  33080]   INFO - ution.rmi.RemoteProcessSupport - Port/ID: 21325/Maven3ServerImpl5ed05101 
2014-01-12 02:57:49,424 [  33563]   INFO - s.impl.stores.FileBasedStorage - Document was not loaded for $APP_CONFIG$/remote-servers.xml file is null 
2014-01-12 02:57:50,185 [  34324]   INFO - tor.impl.FileEditorManagerImpl - Project opening took 13482 ms

Version 0.4.1 was behaving very well for me.

Update: Gave up trying to get version 0.4.2 to work. Tried just about everything like disabling non essential running processes, increasing swap file size. Re-installed 0.4.1 and the project loads up perfectly. — Carlos Taylor, Jan 12 '14 at 08:31
i think it is just a bug in AS. i upgraded to 0.4.2 and my project does not work too, but i get a different error. With AS 0.3.x everything worked well — Laurynas Mališauskas, Jan 13 '14 at 14:25
same here, updating to 0.4.2 also broke everything in my case... It has nothing to do with memory usage : I've got 8 gig of memory and I have 3.5 gig free atm, so not having enough memory to start up a JVM is bullocks... Actually it might have something to do with Gradle versions, I looked into the error log and found this : — TiGer, Jan 14 '14 at 08:03
just now tried with the simple app with AS and it broke as suggested. II think eclipse is the right way to go (for now)... — codebased, Jun 18 '14 at 22:17

Carlos Taylor · Accepted Answer · 2014-01-17T08:26:48.407

293

I'm assuming I can answer my own question.... This worked for me.

File -> Invalidate caches / Restart
Shutdown Android Studio
Rename/remove .gradle folder in the user home directory
Restart Android Studio let it download all the Gradle stuff it needs
Gradle build success !
Rebuild project.... success !

Out of curiousity I compared the structure of the old .gradle and the new one... they were pretty different !

So I'll see how 0.4.2 goes :)

edited Jan 17 '14 at 08:26

answered Jan 16 '14 at 17:20

Carlos Taylor

4,717
3
16
16

1

I tried deleting build.gradle from same level than src and it didn't worked. What did I do wrong? – Ángel Carlos del Pozo Muela Jan 17 '14 at 01:55
2

I wouldn't do that. Just follow the step by step instructions above and it should work if you had the same problem as I did. – Carlos Taylor Jan 17 '14 at 02:32
"Rename .gradle file out of the way". I tried changing its name for example to "___build.gradle" and it didn't work. What did you mean to? – Ángel Carlos del Pozo Muela Jan 17 '14 at 07:42
I renamed mine to old.gradle and it worked. You said earlier that you deleted the build.gradle file from the src directory. I didn't do this as the file is needed in the build. Try creating a new project, if you get the "Gradle project sync failed" error then follow the steps above and report back. – Carlos Taylor Jan 17 '14 at 08:09
Instruction worked for me, but I had to remove/rename ".gradle" folder from user home directory, not the one placed in project workspace. – Ramps Jan 17 '14 at 08:21
1

That should make it clearer Ramps. Have edited my instruction to reflect this. Cheers – Carlos Taylor Jan 17 '14 at 08:27
Eventually this worked for me as well, had to try a couple of times though, so you might have to persist a little. – Bart Enkelaar Jan 20 '14 at 21:33
In my project there are three main folders; .idea, app & gradle. The gradle folder is the one I renamed to old.gradle, but it never solves the problem. I've tried twice. Any advice? – KFP Feb 21 '14 at 16:09
2

KFP the gradle folder that you need to rename is the one in your user directory, NOT the one in your project. See Ramps comment above. Also, my .gradle directory in my user directory looks like this C:\Users\Carlos Taylor\.gradle. That is the one you have to rename/remove. – Carlos Taylor Feb 23 '14 at 11:36
This worked for me without step 3. I had tried a few solutions before that so it might have affected the process, but this step may not be necessary. – The Fish Jun 19 '14 at 14:00
First try with only making **Invalidate cache and restart**. Sometimes this issue solved only with only making this trick – Rohit Patil Dec 26 '17 at 04:34

frogatto · Answer 2 · 2022-12-27T11:10:50.167

72

I had the same problem, but finally I could solve it forever.

Delete gradle and .gradle folders from your project folder.
In Android Studio: Open your project then: File -> settings -> compiler -> gradle: enable offline mode
Note: In relatively newer Android Studios, Offline mode has been moved to gradle setting.
Close your project: File -> close project
Connect to the Internet and open your project again then let Android Studio downloads what it wants

If success then :)
else

If you encounter gradle project sync failed again please follow these steps:
Download the latest gradle package from this directory
Extract it and put it somewhere (for example f:\gradle-1.10)
Go to your Android Studio and load your project then open File->Settings->gradle, in this page click on Use local gradle distribution
Type your gradle folder address there

Congratulation you are done!

edited Dec 27 '22 at 11:10

answered Feb 24 '14 at 19:12

frogatto

28,539
11
83
129

2

This is really work for me.I have just followed the first step and it turn out to be OK. Many Thanks and hope help others. – Kevin May 08 '14 at 16:29
3

Please update gradle link to its folder `http://services.gradle.org/distributions/` instead of file. current gradle is 2.3 – AaA Mar 04 '15 at 03:30
4

In Android Studio 1.5.1, **Files > settings > Build, Execution, Deployment > Build Tools, Gradle > Offline work** – Sithu Feb 18 '16 at 02:44

score 16 · Answer 3 · edited Mar 05 '14 at 01:51

same here, updating to 0.4.2 also broke everything in my case... It has nothing to do with memory usage : I've got 8 gig of memory and I have 3.5 gig free atm, so not having enough memory to start up a JVM is bullocks...

Actually it might have something to do with Gradle versions, I looked into the error log and found this :

2014-01-14 09:00:30,918 [ 61112] WARN - nal.AbstractExternalSystemTask - Project is using an old version of the Android Gradle plug-in. The minimum supported version is 0.7.0. Please update the version of the dependency 'com.android.tools.build:gradle' in your build.gradle files.

You are using Gradle version 1.8, which is not supported. Please use version 1.9. Please point to a supported Gradle version in the project's Gradle settings or in the project's Gradle wrapper (if applicable.) com.intellij.openapi.externalSystem.model.ExternalSystemException: Project is using an old version of the Android Gradle plug-in. The minimum supported version is 0.7.0. Please update the version of the dependency 'com.android.tools.build:gradle' in your build.gradle files

-

You are using Gradle version 1.8, which is not supported. Please use version 1.9.

Please point to a supported Gradle version in the project's Gradle settings or in the project's Gradle wrapper (if applicable.)

OK, I fixed it myself... In the project directory go to /gradle/wrapper directory and edit the gradle-wrapper properties file to this :

distributionUrl=http\://services.gradle.org/distributions/gradle-1.9-all.zip

After open your project in Android Studio and select the build.gradle file in the /src directory and edit it to this :

dependencies {
        classpath 'com.android.tools.build:gradle:0.7.+'
    }

After fixing it like this I discovered this article : http://tools.android.com/recent/androidstudio040released

TiGer, your solution worked for me. I did not need to consult the article. Thank you. — Dick Lucas, Jan 14 '14 at 23:16
This sounds promising. Will have another crack at 0.4.2 and get back. — Carlos Taylor, Jan 15 '14 at 01:55
Still no success with 0.4.2 The project loads and Gradle starts to build but stops with the 'Gradle project sync failed." error. The log file shows this: 2014-01-17 00:19:22,809 [ 89902] INFO - .project.GradleProjectResolver - Gradle project resolve error org.gradle.tooling.GradleConnectionException: Could not run build action using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.9-all.zip'. — Carlos Taylor, Jan 16 '14 at 16:23
Thanks ! I personnally changed it to http\.../gradle-1-9-bin.zip and it worked. — Timores, Feb 07 '14 at 09:06

score 9 · Answer 4 · edited Jun 16 '16 at 11:58

9

Open File-> Settings
Choose Gradle
Mark "Use local grandle distribution" and select the path of grandle home for ex: C:/Users/high_hopes/.gradle/wrapper/dists/gradle-2.1-all/27drb4udbjf4k88eh2ffdc0n55/gradle-2.1.1 then choose service directory path C:/Users/high_hopes/.gradle
Apply all changes
Open File-> invalidate caches/ restart ...
Select Just Restart

edited Jun 16 '16 at 11:58

pRaNaY

24,642
24
96
146

answered Nov 14 '14 at 10:34

high_hopes

133
2
7

score 5 · Answer 5 · answered Jan 24 '14 at 20:55

After reporting the problem on the Android Studio feedback site, they found a solution for me. I am now using Gradle 1.10 and Android Studio 0.4.3.

Here is the link to the page with a description of how I fixed mine: https://code.google.com/p/android/issues/detail?id=65219

Hope this helps!

score 4 · Answer 6 · edited Jun 30 '14 at 18:04

I found one answer on the net and it worked for me, thus here it is:

When you get the gradle project sync failed error, with error details:

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, on Windows, please go to:

Control Panel > System > Advanced(tab) > Environment Variables > System Variables > New:

Variable name _JAVA_OPTIONS and Variable value -Xmx512M

Save it, restart AS. It might work this time, as it did for me.

Source: http://www.savinoordine.com/android-studio-gradle-windows-7/

score 3 · Answer 7 · answered Mar 04 '14 at 04:40

I am facing this problem many times from last few days, the answer above works perfectly fine. I was looking for the exact reason for this problem and in my case I found slow internet or no internet on your machine(assuming you are taking project to windows from mac, that may not be required).

I've noticed while doing build it stopped fetching a URL(http://.maven.org/). I don't know why android studio doing these things again, but that seems to be the only problem in my case.

score 3 · Answer 8 · answered Dec 12 '14 at 00:48

3

For those who are upgrading to v1.0 of Android Studio and see the error Gradle DSL method not found: 'runProguard', If you are using version 0.14.0 or higher of the gradle plugin, you should replace "runProguard" with "minifyEnabled" in your build.gradle files. i.e.

buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
    }
}

answered Dec 12 '14 at 00:48

Reefwing

2,242
1
22
23

Was actually about to delete my small project on which this error occured. Saved me an hour of programming. :) – Edwin Lambregts Dec 12 '14 at 11:10

score 2 · Answer 9 · answered Jun 23 '14 at 14:07

2

After following Carlos steps I ended up deleting the

C:\Users\MyPath.AndroidStudioPreview Directory

Then re imported the project it seemed to fix my issue completely for the meanwhile, And speedup my AndroidStudio

Hope it helps anyone

answered Jun 23 '14 at 14:07

shimi_tap

7,822
5
23
23

score 2 · Answer 10 · answered Oct 13 '14 at 18:33

I have Android Studio 0.8.9 and after hours on forums the thing that finally worked for me was to manually download Gradle (latest version) then go to: C:\Users\.gradle\wrapper\dists\gradle-1.12-all\\ and replace the local archive with the recently downloaded archive and also replace the extracted data; after restarting Android Studio... he did some downloadings and builds and all sorts of stuff, but it finally worked.. Good Luck people!

score 2 · Answer 11 · answered Jan 01 '15 at 00:49

2

This is what worked for me with Android Studio 1.0.2:

File -> Settings-> Gradle Set 'Use default Gradle wrapper.'

The other methods didn't seem to work for me.

answered Jan 01 '15 at 00:49

user1123966

208
2
5

score 2 · Answer 12 · answered Jun 08 '15 at 20:58

2

I'm not using Android Studio, but had same problem. I had to update the latest java jdk and set the JAVA_HOME to that jdk.

answered Jun 08 '15 at 20:58

Niels Steenbeek

4,692
2
41
50

score 1 · Answer 13 · answered Jan 29 '15 at 05:14

1

I had the same error. I deleted the android repository from android sdk manager and reinstalled it. It worked.

answered Jan 29 '15 at 05:14

Rajani

11
1

score 1 · Answer 14 · answered Jan 10 '16 at 05:38

1

Load Project:>Build, execution, Deployment:>(Check on)compiler Independent modules in parllel.

answered Jan 10 '16 at 05:38

Atul Shukla

11
1

score 0 · Answer 15 · answered Jan 11 '14 at 19:17

0

Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.

seems fairly clear-cut: your OS can't find enough RAM to start a new Java process, which is in this case the Gradle builder. Perhaps you don't have enough RAM, or not enough swap, or you have too many other memory-hungry processes running at the same time.

answered Jan 11 '14 at 19:17

Scott Barta

79,344
24
180
163

I had no problems with version 0.4.1 though. I could have Chrome running with 8-10 tabs open as well as a Genymotion emulator instance. – Carlos Taylor Jan 11 '14 at 19:24
1

Also, I just fired up Eclipse 4.2.2 and it loads the project fine. I know that AS may probably have a lot more overhead but my workspace in Eclipse has about 15 projects loaded at the same time! Seems to me like AS 0.4.2 has gone a step backward in memory management compared to 0.4.1 and overall cannot compare to Eclipse at this point in time IMHO. – Carlos Taylor Jan 11 '14 at 19:32

RavenShield · Answer 16 · 2014-05-14T13:17:04.717

0

I had this problem when I started my project and there was not enough RAM for gradle. I searched a solution for an hour including the variants given above, but then I just closed my browser and rebooted my IDE. Interesting that if you run browser or a game after successful starting IDE and project it still works properly. Hope this solution will be useful for somebody. p.s. sorry for my English knowledge (it`s from school).

edited May 14 '14 at 13:17

answered Apr 11 '14 at 19:20

RavenShield

11
1

You might want to say how you know there was not enough RAM for gradle and the results of the other things you tried. – Edward Apr 11 '14 at 19:41
I just tried more hard solutions, but solved my problem in easy way and hoped that it will help to somebody else. Each time I run AndroidStudio I must close all applications in order not to have this error. – RavenShield Apr 24 '14 at 20:14

score 0 · Answer 17 · edited Jun 06 '14 at 14:07

0

All you have to do is remove .gradle from user, paste, and verify update in Android Studio and it will work perfectly!

edited Jun 06 '14 at 14:07

4444

3,541
10
32
43

answered Jun 06 '14 at 13:45

Supertramp

1

score 0 · Answer 18 · answered Nov 05 '14 at 13:07

0

I always remove the .gradle folder from %USERS% folder and start the studio again. When starting the IDE it downloads gradle again with all the dependencies again. Its work PERFECT.

answered Nov 05 '14 at 13:07

Ashraf Sayied-Ahmad

1,715
2
18
21

score 0 · Answer 19 · answered Jan 06 '15 at 14:01

Today I ran into the same error, however, i was using Android Studio 1.0.2. What i did tot fix the problem was that i started a project with minimum SDK 4.4 (API 19) so when i checked the version i noticed that at File->ProjectStructure->app i found Android 5 as a compile SDK Version. I changed that back to 4.4.

score 0 · Answer 20 · edited May 23 '17 at 10:31

0

I was seeing this error along with: "Error:compileSdkVersion android-21 requires compiling with JDK 7"

For me, the solution was found here, where I had to update the JDK location in the project structure.

edited May 23 '17 at 10:31

Community

1
1

answered Jan 22 '15 at 20:12

user1720817

125
6

android studio 0.4.2: Gradle project sync failed error

20 Answers20

Linked

Related