5 ways to reduce Android Studio RAM usage
1 Kill Gradle daemons after builds
Run './gradlew --stop' when you're done building. Gradle daemons persist for 3 hours by default, consuming 500 MB–2 GB each.
2 Use a physical device
The Android emulator consumes 1–4 GB. A physical device connected via USB uses zero RAM on your Mac.
3 Close the emulator between tests
If you must use the emulator, close it between test runs. Re-launching is fast with snapshots.
4 Reduce Gradle daemon memory
In gradle.properties, add 'org.gradle.jvmargs=-Xmx2g' to limit the daemon's heap.
5 Same IntelliJ tips apply
Android Studio is an IntelliJ fork — all IntelliJ memory tips (heap tuning, excluding directories, closing unused projects) work here too.
How DevPulse helps with Android Studio
DevPulse groups Android Studio's JVM, Gradle daemons, and emulator processes into one unified view. It detects zombie Gradle daemons from previous build sessions.
Instead of guessing how much RAM Android Studio consumes or manually checking Activity Monitor, DevPulse gives you a clear, always-visible answer in your menu bar.