在更新到Android Studio 2后,当我试图运行我的应用程序并选择一个模拟器时,我等待模拟器启动,它突然被杀死。我可以看到模拟器进程几分钟,但从来没有GUI。在Android studio中,我得到了错误

android studio Error while waiting for the device: The emulator process for AVD was killed

即使我在Android Studio之外运行模拟器也会发生这种情况。我试用了Android 6和基于Android 4.4的模拟器。 在Windows 7 x64 PC上运行。类似于另一个StackOverflow帖子被关闭。我尝试了各种ram、VM堆和分辨率设置。


当前回答

我把图形换成了软件,已经安装了英特尔x86模拟器,并重新启动了PC。毫无效果。这是Hyper-V问题。我已经关闭了VMWare。我打开它,重新启动PC和模拟器工作。所以请试试Hyper-V。

其他回答

如果你把这些加到~/。ZSHRC(或~/。zprofile,…)

export ANDROID_SDK_ROOT=...
export ANDROID_SDK_HOME=...

它会导致这个错误。

删除或注释这些行,然后重新启动Android Studio,它将工作。

我把图形换成了软件,已经安装了英特尔x86模拟器,并重新启动了PC。毫无效果。这是Hyper-V问题。我已经关闭了VMWare。我打开它,重新启动PC和模拟器工作。所以请试试Hyper-V。

以我为例,在我尝试了较低版本的Pixel和Android后,问题得到了解决。

也许问题是你已经安装Android Studio在一个非默认目录(例如c:\your_pesonal_directory),也许你有你的用户在ascii字符(如papà)为此,Android不能访问ascii目录

要在Win10上解决这个问题:

输入C:\users\你的用户名\ 将.android目录移动到另一个目录示例 C: \ AndroidSDK \ .android 创建环境变量(进入设置并在搜索工具栏中写入环境变量) 并命名为ANDROID_SDK_HOME 选择ANDROID_SDK_HOME的新路径:C:\AndroidSDK\ .android 重启Android Studio

这个错误非常普遍,这种症状可能是由于一百万个完全不同的问题中的任何一个造成的。 你要做的是找到更多关于正在发生的事情的信息,这样你就不会看起来像一只瞎鸡在啄食令人作呕的石头。 因此,让我们得到调试步骤:

first thing is to find the logs of Android studio. In doubt, stackoverflow already has a section to help you How to find the logs on android studio?. The text file should be named: "idea.log". You can open it with notepad, but only open it after android studio is closed (in windows 10). There will be a lot of events inside. Search by "manager.EmulatorProcessHandler" and the last date that you had the error. A good trick to facilitate your life, after having found the log file, is to close Android studio: delete the log file; reopen android studio and retry to open the emulator. The log file will be recreated with a lot less history and so it will be so much easier to search. In my case, i found: manager.EmulatorProcessHandler - Emulator: emulator: ERROR: Another emulator instance is running. Please close it or run all emulators with -read-only flag.. Given that, it is easy to solve. I just had to open a process manager and terminate the emu process that didn't correctly close for some unknown reason. Of course, in our case the log will be completely different. But now you have a clue of the hidden criminal.