Android Studio emulator: Process finished with exi

2020-01-29 05:21发布

问题:

My android studio emulator not starting. I'm using Android Studio 3.0 on Ubuntu 17.10

Error - Emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

回答1:

I solved it by going into my virtual device's settings and changing "Emulated Performance" from "Automatic" to "Software".



回答2:

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



回答3:

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/



回答4:

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



回答5:

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.



回答6:

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



回答7:

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.



回答8:

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.