Why is Android Studio using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Android Studio is several heavy programs at once: the IDE itself runs on a Java virtual machine, Gradle and Kotlin compile your app in separate daemon processes, and the Android Emulator runs a whole virtual phone. Each has its own memory limit, and together they can take a large share of a Mac's memory. Google's documentation covers adjusting heap sizes in Memory Settings, Power Save Mode, and debugging on a physical device to save memory.
Which processes does Android Studio start?
- Android Studio: the IDE. Google states its default maximum heap is 1280 MB, and it suggests a higher value when a project needs it.
- Gradle daemon and Kotlin daemon: build processes that run on the JVM and appear as java in Activity Monitor. Gradle's default maximum heap is 1,536 MB, according to Google.
- Android Emulator: runs the virtual device, as qemu-system-aarch64 on Apple silicon Macs. Google notes that debugging on an emulator uses more memory than on a physical device.
Why does Android Studio use so much CPU?
Indexing after you open a project or change branches, Gradle sync, and builds all run on several cores. In the editor, on-the-fly inspections and error highlighting re-analyze code as you type, and lint checks run on top. The emulator uses CPU continuously while it runs, even when the app on it is idle.
How do you make Android Studio lighter?
- Set the heap sizes. Open Settings (Command-comma), then Appearance & Behavior > System Settings > Memory Settings, and adjust the heap sizes for the IDE, Gradle and Kotlin. Restart Android Studio after changing the IDE heap. Google notes that allocating too much memory can degrade performance.
- Turn on Power Save Mode. Choose File > Power Save Mode. It turns off error highlighting and on-the-fly inspections, auto-popup code completion and automatic incremental background compilation.
- Debug on a physical device. Run your app on a connected phone instead of the emulator when you can, which saves the emulator's memory and CPU.
- Trim lint checks. In Settings, open Editor > Inspections and deselect checks you do not need.
- Keep parallel compilation off on low-memory Macs. In Settings > Build, Execution, Deployment > Compiler, leave Compile independent modules in parallel unchecked if the Mac is short of memory.
When is Android Studio's memory use a problem?
It is a problem when memory pressure in Activity Monitor turns yellow or red and the Mac starts swapping heavily. Count all of Android Studio's processes together: the IDE, each java daemon and the emulator. Android Studio also checks for heap size optimizations itself and shows a notification when it thinks a different setting would help.
How can Thrum help with Android Studio?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much Android Studio holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click Android Studio in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
What is the default memory limit for Android Studio?
Google's documentation states a default maximum heap of 1280 MB for the IDE and 1,536 MB for the Gradle daemon.
Why do I see java processes after closing Android Studio?
Gradle and Kotlin daemons can outlive a build so the next one starts faster. They exit after a period of inactivity, or you can stop Gradle daemons with ./gradlew --stop in the project.