Android Studio emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

I solved this problem by changing my graphics driver from Software and Updates. Head over to Additional Drivers and Use the proprietary and tested one. Check if it helps. Thanks

Changing "Emulated Performance" from "Automatic" to "Software" was a temporary solution for me (I am on Linux btw). The simulator would crash in a few seconds.

Instead this did it for me:

cd ~/Development/Android/Sdk/emulator/lib64/ mv libstdc++ libstdc++.bak

credit: https://cialu.net/android-studio-how-to-solve-emulator-libgl-error-on-ubuntu-systems/

I have this problem to Emulated Performance = software doesn't help, because your emulator will be broken and can not be working if your app needs more process...

I have Ubuntu 18 and install my graphics card Nvidia, and it's solved now

for ubuntu you can try it:

For Nvidia

sudo apt-get install nvidia-352  "nvidia-352 is an EXAMPLE In my Device"

and For AMD

sudo apt-get install fglrx

more details:

enter link description here

When use Linux spatially Debian and Ubuntu after update card graphic driver or etc. this problem happening often.

So you need just reboot your OS

Restarting the computer worked for me.

Changing the Emulated Performance from automatic to software made it work, but at least on Ubuntu, that has a poor performance.

I solved this issue by simply creating a new virtual device.

The problem is in the linux video card, to solve in Ubuntu 18 or derivatives, just go to "Programs and Updates" -> "Additional Drivers" and select the proprietary driver of your video card and then restart the computer. It resolved for me.

I had the same error tried starting emulator. I am installing android studio 3.5 on Ubuntu 18.04 and NVIDIAM GF119. In Software and Updates, under Additional Drivers tab, I chose the proprietary tested driver for my Graphic card. Then the emulator works.

Found everyone's solution was not working for me. Updated video card on linux and still had the issue.

What worked was changing the number of processor cores available to the emulator from 4 to 2.

I tried the other solutions, but this makes sense as I have 8 processor cores and may need to have several emulators open.

My current configuration is shown in the attached image my emulator configuration

This is most likely an issue with your graphics card driver, i would recommend doing a clean re-install of the driver if it doesn't fix itself on reboot.

For flatpak users on linux, i recommend running "flatpak update" in the terminal to update your GPU dependencies for flatpak (it typically breaks if you update your GPU driver and not flatpak GPU libs), this is what resolved the issue for me.

I made this answer because switching to software rendering isn't really a solution, it's more of a dirty workaround, and will only waste your CPU utilization.

I'm using Ubuntu 20.04.2 and driver install solved the problem.

sudo ubuntu-drivers autoinstall

After finishing the install, need to reboot.

reboot

I had the same problem, my emulators were stopping with SEGV. Both on software and hardware graphics. But after looking in journalctl it was apperantly SELinux that was blocking the emulator. Here I used the SELinux troubleshooter to add a bypass and after that the emulator booted fine.

select this update.work for me.

I was getting the same error using intel graphics on ubuntu 20.04 on a lenovo yoga 260. I tried lots of answers on stack overflow, and none seemed to work. I could not select 'software' from the gui rather than auto. But then I found this page: https://developer.android.com/studio/run/emulator-acceleration And I ran this at the command line and it worked. I don't care if it's slow: at least it doesn't crash.

cd ~/Android/Sdk/emulator
./emulator -avd Pixel_2_API_30 -gpu swiftshader_indirect

I solved this issue by changing the permissions for the img files

cd /home/[your_user]/.android/avd/[device_name]_API_[API_version].avd
chgrp libvirt *.img
chmod 766 *.img

In the SDK Manager, under SDK Tools tab, make sure that you've the latest "Android Emulator".