#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread how to#
#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread update#
#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread software#

#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread how to#

The executable doesn't have symbols so I'm not sure how to point the original developer to the root cause, but here is the threads state: (gdb) info threadsДЎ Thread 0x7f6d20428700 (LWP 14472) 0x00000000014e8baf in ? ()Дў Thread 0x7f6d20c29700 (LWP 14471) syscall () at.

#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread update#

I started experiencing the exact same problem after the most recent update of the Android SDK on my Ubuntu 16.04. In that case, you may want to try to reverse the steps above if IPv6 is already enabled on your system and the emulator does not start.

Update Jan 5, '18: At least one user reports that disabling a previously enabled IPv6 has resolved the problem on his system. If you see 1 above, edit your /etc/nf file and comment out all the IPv6 disable directives: # .disable_ipv6 = 1 $ cat /proc/sys/net/ipv6/conf/all/disable_ipv6 I found an interim workaround - make sure IPv6 is enabled. What's causing the 'QEMU2 main loop' to hang, and how can I fix it? My SDK tools menu doesn't have an entry for emulator accelerator (HAXM), though my PC has an Intel CPU: I shouldn't have to change this since my AVD worked just yesterday! What broke? libstdc++ 6.0.21 into the SDK emulator lib64/libstdc++ folder, I even downloaded Android Studio and ran a fresh installation with its own new SDK folder with freshly downloaded SDKs, I tried creating new AVDs with different architectures (arm) and different API levels (24, 27), I tried restarting ADB, and even restarting the computer.

#Android emulator mac android studio crashes detected hanging thread qemu2 cpu0 thread software#

(I verified that the emulator is still installed via the SDK Manager, I tried switching between the software and the hardware graphics settings of the AVD, I tried replacing libstdc++ with a newer version 6.0.24, I tried instead to ln -sf my /usr/lib.

I tried the solutions suggested in all the threads describing similar emulator problems. Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

My AVD worked perfectly before, but after the update finished, now when I launch it, it shows a black screen in the emulator window for 15 seconds and then crashes with the following error message: ERROR: detected a hanging thread 'QEMU2 main loop'. It then notified me that it had successfully updated the emulator. Yesterday, Android Studio popped up a message saying that there's an update available, and I always click those. I use Android Studio 3.0.1 on Ubuntu 16.04.