在更新到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堆和分辨率设置。
如果你的用户名不是ascii/有空格,那么这可能会有帮助,因为我尝试了这里所有的解决方案,不能解决这个问题:
注:我在这个视频中找到了这个解决方案,是一个叫“tatachka”的用户建议的,这是她的评论(她很友好地让我分享在这里)。
For example, I had this path
c:\Users\Таня.android\avd\Nexus_One_API_24.avd My name in Windows is
Таня, written in Cyrillic in windows encoding (cp1251). I changed the
path to e:\Distribu\AVD.android\avd\Nexus_One_API_24.avd I moved
files from disk C there and edited Nexus_One_API_24.ini changing the
path in it and everything worked.
How to change the folder path: My computer -> properties -> advanced
system parameters -> environment variables - > lower 'New...' button:
variable name: ANDROID_SDK_HOME variable value: e:\Distribu\AVD
(in my case)
After the reboot, a new folder(.android) appears in the folder
e:\Distribu\AVD containing the 'avd' folder
编辑:为了澄清,这里的想法是您不希望路径具有非ascii字符。我把它移动到C:\programs_that_cant_read_hebrew(并执行了其他步骤),它工作得很好。
编辑:在注释后将“英文”更改为“ascii/空格”
这个错误非常普遍,这种症状可能是由于一百万个完全不同的问题中的任何一个造成的。
你要做的是找到更多关于正在发生的事情的信息,这样你就不会看起来像一只瞎鸡在啄食令人作呕的石头。
因此,让我们得到调试步骤:
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.