在更新到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堆和分辨率设置。
当前回答
这个错误非常普遍，这种症状可能是由于一百万个完全不同的问题中的任何一个造成的。 你要做的是找到更多关于正在发生的事情的信息，这样你就不会看起来像一只瞎鸡在啄食令人作呕的石头。 因此，让我们得到调试步骤:
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.
其他回答
这个错误非常普遍，这种症状可能是由于一百万个完全不同的问题中的任何一个造成的。 你要做的是找到更多关于正在发生的事情的信息，这样你就不会看起来像一只瞎鸡在啄食令人作呕的石头。 因此，让我们得到调试步骤:
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.
我的棘手的解决方案是尝试启动另一个模拟器，然后启动这个坏的模拟器。
在我的情况下(一个主256堆是坏的)，我将开始一个主512堆，然后开始一个主256堆
当我把我的SDK位置从一个磁盘更改到另一个磁盘时，这个问题发生在我身上，由于磁盘空间有限的问题，而这样做的一些文件可能会损坏或丢失，经过一番挖掘，我发现我的SDK被部分安装(根据SDK管理器)。 我所要做的就是从SDK管理器中重新下载剩下的文件来解决这个问题。
这些答案对我都没用。我只是用相同的设置创建了一个新的虚拟设备，并删除了旧的。新的工作很好。
如果您使用McAfee防病毒和Windows 10，这可能会帮助您:
根据snehatilak的建议，卸载并重新安装Android Emulator最初对我的情况有所帮助，但第二天模拟器又死机了。
我发现McAfee杀毒软件已经隔离了文件avd .conf，原来是在C:\Users[username].android\avd[avdImage]\
在恢复AVD.conf并从扫描中排除它之后，它似乎又好了。
这一切都始于2021年2月2日，我猜是在McAfee更新之后。
以下是步骤:
首先转到“设置”下的“隔离项目”并恢复AVD.conf文件
然后转到“设置”下的“实时扫描”，在你创建的每个模拟器中排除AVD.conf。(位于C:\Users[username].android\avd[avdImage])
