1

I am getting gradle build error while running the app. I am using windows 10 with 8GB RAM, Android studio version 4.0.1

Out of memory: Java heap space. Please assign more memory to Gradle in the project's gradle.properties file. For example, the following line, in the gradle.properties file, sets the maximum Java heap size to 1,024 MB: org.gradle.jvmargs=-Xmx1024m

Even after following the same steps I am not able to run the app. Could anyone help with a permanent solution for this error???

Here is my gradle.properties file:

android.enableJetifier=true
android.useAndroidX=true
org.gradle.jvmargs=-Xmx1024m
Kartika Vij
  • 185
  • 2
  • 15

3 Answers3

2

Adding android:largeHeap="true" to the AndroidManifest.xml may solve your problem, if you haven't already added. But note that the main issue is your app is consuming too much memory. Consider tracking your app at runtime to find the unusual memory consuming process/objects.

<manifest 
     ...
     <application 
         android:largeHeap="true"
         ...

     </application>
</manifest>
sajjad
  • 712
  • 4
  • 10
  • I have already added, it worked once but when I tried to run again then same error – Kartika Vij Jul 25 '20 at 12:33
  • There can be many possibilities leading to `OutOfMemoryException`. `ListView`s, too many living `Fragment`s, loading high quality images etc. So try to figure out the memory killer objects in your code. – sajjad Jul 25 '20 at 12:38
  • This for app when u can build, the error message appear when he building the project – Thuan Tang Jul 25 '20 at 12:50
  • Yes I am not able to run my app then how would I figure out anything? – Kartika Vij Jul 25 '20 at 12:58
1
  1. Give more RAM for gradle org.gradle.jvmargs=-Xmx4g
  2. If you face the same problem after can run for a few times, open Task Manager, End task any Open JDK Platform binary or Java(TM) Se Binary to release RAM, then you can run project again.

If your computer have less than 8GB RAM, set like this in your gradle.properties org.gradle.jvmargs=-Xmx2048M

Thuan Tang
  • 61
  • 5
1

I'm working on a big android project with multiple modules and flavors and had the same problem.

I tried everything from tweaking memory to cleaning project, restarting while invalidating cache, deleting sources and recloning from repo.

I ended up deleting the ".gradle" folder in my user folder and recloning my project.. and it worked. Lost a lot of time on this though.

AlexMok
  • 694
  • 5
  • 18