Android emulator crashing on Mac

Question

When I try to launch Android emulator, it crashes on Mac OS X. It was working some time ago, but now it isn't and I don't have an idea why.

Crash log: http://pastebin.com/04MjCqaS

Terminal log in verbose mode: http://pastebin.com/L6y6rUr0

Answer 1

Same issue here, I'm running a mac mini with 8GB of RAM and MacOS Lion. It used to work with the old AVD with some random crashes every now and then but since the last update to APi 17 it's a pain in the neck.

The ADT bundle doesn't work at all. After tweaking the memory limits on eclipse.ini file it throws random memory errors. Also it's not been able to download and install the m2e (maven to eclipse) plugin.

I moved to IntelliJ and I'm able to launch AVD manager but none of the "old" created devices work. If I create a new one and I launch it it works until I close it, then I have to restart the Mac and create a new device. Also it randomly shows errors when I want to delete those old created virtual devices.

Also the DDMS fails to start. I launch it, shows its icon on the Dock but it doesn't respond until I force close. What a Nightmare.

** EDIT ** I found at android dev bug tracker this issue when you're running 2 screens: here

This is happening to me with the android emulator. I solved it like this: cd ~/.android/avd ls *.avd

Now choose the emulator that is crashing and

cd name_of_the_emulator.avd
touch emulator-user.ini
vi emulator-user.ini

And now reset window.x, that's window.x=0 exit and run the emulator.

If you move and close the emulator to the secondary screen it will crash the next time you want to run it.

Answer 2

Kill your Docker process

One problem I have seen multiple time is with Docker. Android Emulator crashes when Docker is running on Mac.

Answer 3

I was following the PhoneGap "Getting Started" guide for Android, and when I got to "Deploy to Emulator," after I created a new AVD, my Mac would crash and reboot. I stumbled on this thread, but thought it worth mentioning that what actually solved the problem for me was an Intel patch for the Hardware Accelerated Execution Manager located here: http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager