Emulator seems to freeze, but it's not frozen the frames have just stopped coming in, if you move the tool window then it updates the emulator frame [312677259]

Fixed

Bug

Status Update

No update yet.

Description

co...@protonmail.com

created issue #1

Nov 22, 2023 02:15PM

Have this happening on both my work and personal computer. I'm using canary 14 of AS and latest emulator that you get in that version of AS.

I'll try to get more details, but wanted to bring it up at least.

Comments

jl...@google.com <jl...@google.com> #2Nov 22, 2023 04:16PM

Assigned to an...@google.com.

Hi, some users reported that installing "Vulkan SDK" helps with this issue. What is your GPU and its driver versions?

rk...@google.com <rk...@google.com> #3Nov 22, 2023 06:30PM

Reassigned to rk...@google.com.

WARN - Emulator: Pixel 9 Pro XL API 35 - Vanguard anti-cheat software is detected on your system. It is known to have compatibility issues with Android emulator. It is recommended to uninstall or deactivate Vanguard anti-cheat software while running Android emulator.
2024-12-03 13:34:02,503 [ 53041] INFO - #com.android.adblib.impl.SessionDeviceTracker - trackDevices() failed, will retry in 2000 millis, connection id=32
java.lang.IllegalStateException: ADB location has not been initialized

ok...@gmail.com <ok...@gmail.com> #4Nov 23, 2023 10:19AM

Hi, I have installed the Vulkan SDK on my PC, and my GPU is an NVIDIA GeForce RTX 3060 Laptop GPU with driver version 30.0.15.1274. I also tried deactivating the Vanguard anti-cheat, but the AVD still terminated. I’ve attached the log file after deactivating Vanguard.

Regarding the ADB issue ("ADB location has not been initialized"), I ran the adb version command in Command Prompt and successfully retrieved the version. Could you help me check this again?

Screen Recording 2023-11-23 at 11.14.20.mp4

20 MB

Download

rk...@google.com <rk...@google.com> #5Nov 23, 2023 08:21PM

Reassigned to ja...@google.com.

Could you please try stating the Emulator from the command line this way

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
emulator.exe -avd Pixel_9_Pro_XL_API_33 -wipe-data -no-snapshot -verbose -feature -Vulkan

and attach its output? If you notice any popups about missing dlls please include them here.

as_settings.png

153 KB

View

Download

ok...@gmail.com <ok...@gmail.com> #6Nov 24, 2023 01:16PM

Hi this is the output txt flle

ch...@gmail.com <ch...@gmail.com> #7Nov 24, 2023 08:49PM

Thank you, please try adding -gpu swangle (this is a software GPU, it will be slow), I think for whatever reason we can't talk to your GPU.

Please consider trying the latest version we have here:

https://developer.android.com/studio/emulator_archive

vokoscreenNG-2023-11-24_17-37-05.mkv

6 MB

Download

ja...@gmail.com <ja...@gmail.com> #8Nov 27, 2023 11:58AM

The attached TXT file contains the output after adding -gpu swangle. Following that, I manually updated the emulator from Android Emulator (35.2.10) Stable to Android Emulator (35.4.3) Canary. I also deleted the old AVD and created a new one, but it still terminated. I’ve attached the report generated after updating the emulator version.

Could you please check this for me?

ch...@gmail.com <ch...@gmail.com> #9Nov 27, 2023 12:21PM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

ig...@gmail.com <ig...@gmail.com> #10Nov 29, 2023 08:06PM

Please check if you have crashreports and if you do consider uploading them (please attach crash ids here):

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
crashreport.exe -l
crashreport.exe -u

rk...@google.com <rk...@google.com> #11Dec 4, 2023 10:20PM

Hi this is the output crash id :

Microsoft Windows [Version 10.0.19045.5131]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -l
C:\Users\crazy\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.4.3.db\reports\fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a.dmp

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -u
Report fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a is available remotely as: 9a9150ec7b65047e

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>

ja...@gmail.com <ja...@gmail.com> #12Dec 4, 2023 10:24PM

Thank you a lot! We got the crash. I think we can't handle zero of VK devices well :) Serdar should know more why we get zero VK devices.

https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/android-ui/modules/aemu-gl-init/src/android/opengl/emugl_config.cpp#525

Maybe we should return false if deviceCount is zero.

ok...@gmail.com <ok...@gmail.com> #13Dec 5, 2023 08:56AM

Does this look related?

https://github.com/KhronosGroup/Vulkan-Loader/issues/552

ch...@gmail.com <ch...@gmail.com> #14Dec 5, 2023 02:08PM

I’m not entirely sure if it’s directly related to the issue I’m facing. If it is, what solutions would you recommend to address this? So far, I’ve noticed that deviceCount is zero, and I suspect it could be related to the Vulkan loader not detecting any devices.

If you have any specific steps or fixes in mind, I’d appreciate your guidance. I can also run additional tests like vulkaninfo or check my Vulkan configuration if needed.

ja...@google.com <ja...@google.com> #15Dec 6, 2023 07:48PM

As I understand, Vulkan-Loader/issues/552 is talking about the case when there are two GPUs: an integrated AMD and a separate NVIDIA and somehow the AMD side prevents returning anything. If this is your case, I think the solution is to update the AMD GPU drivers.

ja...@google.com <ja...@google.com> #16Dec 6, 2023 09:16PM

Hi bro, the AVD is working now! After uninstalling the driver and reinstalling the latest version, the AVD opens successfully. Thank you so much for your help and for taking the time to assist me!

ja...@google.com <ja...@google.com> #17Dec 6, 2023 09:42PM

Thank you for confirming this. We will fix the crash, but all we can do is to say "Your system has no Vulkan devices, update drivers or something" and exit.

ja...@google.com <ja...@google.com> #18Dec 6, 2023 10:04PM

Thank you for the update.

ja...@google.com <ja...@google.com> #19Dec 6, 2023 10:18PM

Thanks for reporting this, a change is submitted (aosp/3393546) and will be available in the next canary builds of the emulator to correctly give an error for zero device cases. I'll close this one now as the booting issue is resolved with a driver update.

bo...@mfour.com <bo...@mfour.com> #20Dec 12, 2023 05:54PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Emulator 35.3.11 Stable

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Message last modified on Dec 12, 2023 06:01PM

ja...@google.com <ja...@google.com> #21Dec 13, 2023 05:10PM

Further fixes for this issue are now available in:

Android Emulator 35.4.5 Canary

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

ja...@google.com <ja...@google.com> #22Dec 14, 2023 05:32PM

Marked as fixed.

https://android-review.git.corp.google.com/c/platform/external/qemu/+/2874534

co...@protonmail.com <co...@protonmail.com> #23Dec 20, 2023 12:08PM

what version of emulator should this be in?

mi...@fresha.com <mi...@fresha.com> #24Dec 20, 2023 12:13PM

I'm testing the latest version 34.1.13 and haven't been able to reproduce the issue

la...@gmail.com <la...@gmail.com> #25Jan 24, 2024 12:18PM

Still seeing this issue with 34.1.15-11228956 in AS Hedgehog 2023.1.1 patch 1

co...@protonmail.com <co...@protonmail.com> #26Jan 25, 2024 03:44AM

FWIW Not seeing this issue anymore in latest canaries/beta.

ok...@gmail.com <ok...@gmail.com> #27Jan 25, 2024 12:47PM

I'm having this issue again, it's re-appearing with the latest update

Android Studio Hedgehog | 2023.1.1 Patch 2
Build #AI-231.9392.1.2311.11330709, built on January 19, 2024

Emulator version : 34.1.13-11169323

el...@gmail.com <el...@gmail.com> #28Jan 29, 2024 11:52AM

I'm having this issue.

Android Studio Iguana | 2023.2.1 Beta 2
Build #AI-232.10227.8.2321.11280706, built on January 5, 2024
Android emulator version 34.1.15.0 (build_id 11228956) (CL:N/A)

Message last modified on Jan 29, 2024 11:52AM

ch...@gmail.com <ch...@gmail.com> #29Jan 30, 2024 06:54PM

This issue come back in Android Studio Iguana | 2023.2.1 Beta 2.

ch...@gmail.com <ch...@gmail.com> #30Jan 31, 2024 02:23PM

The new emulator version with the bug fix is delivered to Jellyfish version but not to Iguana Beta Version. A workaround is to update the emulator using the canary version and go back to beta version.

ad...@gmail.com <ad...@gmail.com> #31Mar 1, 2024 02:09PM

I'm having this issue still.

Android Studio Iguana | 2023.2.1 Build #AI-232.10227.8.2321.11479570, built on February 22, 2024 Runtime version: 17.0.9+0--11185874 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Windows 11.0

Android emulator version 34.1.18.0

Message last modified on Mar 1, 2024 02:10PM

al...@gmail.com <al...@gmail.com> #32Mar 5, 2024 01:46PM

I'm having this issue too

Android Studio Iguana | 2023.2.1
Build #AI-232.10227.8.2321.11479570, built on February 22, 2024
Runtime version: 17.0.9+0--11185874 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4086M
Cores: 12
Registry:
ide.experimental.ui=true

Non-Bundled Plugins:
Dart (232.10286)
com.bloc.intellij_generator_plugin (3.4.0)
io.flutter (78.0.2)

Emulator version: 34.1.18

CPU: Ryzen 5600
GPU: Radeon 6500XT

Message last modified on Mar 5, 2024 01:48PM

xa...@google.com <xa...@google.com> #33Mar 8, 2024 02:52AM

This should be fixed in 34.1.19, please update and let us know.

so...@google.com <so...@google.com> #34Mar 8, 2024 11:41PM

Comment has been deleted.

Message last modified on Mar 11, 2024 03:59PM

so...@google.com <so...@google.com> #35Mar 8, 2024 11:41PM

Note

From now till end of Feb 2024, we are migrating to using a separate task item to track postmortem status, instead of using the original fixed bug. You may run into unexpected issues as we iron out the wrinkles in the automated workflow. Any questions or feedback, please email: android-hygiene-autobug-filer@.

Thank you for your patience and support.

Issue 312677259

Description

Issue summary

Comments

jl...@google.com <jl...@google.com> #2Nov 22, 2023 04:16PM

rk...@google.com <rk...@google.com> #3Nov 22, 2023 06:30PM

ok...@gmail.com <ok...@gmail.com> #4Nov 23, 2023 10:19AM

rk...@google.com <rk...@google.com> #5Nov 23, 2023 08:21PM

ok...@gmail.com <ok...@gmail.com> #6Nov 24, 2023 01:16PM

ch...@gmail.com <ch...@gmail.com> #7Nov 24, 2023 08:49PM

ja...@gmail.com <ja...@gmail.com> #8Nov 27, 2023 11:58AM

ch...@gmail.com <ch...@gmail.com> #9Nov 27, 2023 12:21PM

ig...@gmail.com <ig...@gmail.com> #10Nov 29, 2023 08:06PM

rk...@google.com <rk...@google.com> #11Dec 4, 2023 10:20PM

ja...@gmail.com <ja...@gmail.com> #12Dec 4, 2023 10:24PM

ok...@gmail.com <ok...@gmail.com> #13Dec 5, 2023 08:56AM

ch...@gmail.com <ch...@gmail.com> #14Dec 5, 2023 02:08PM

ja...@google.com <ja...@google.com> #15Dec 6, 2023 07:48PM

ja...@google.com <ja...@google.com> #16Dec 6, 2023 09:16PM

ja...@google.com <ja...@google.com> #17Dec 6, 2023 09:42PM

ja...@google.com <ja...@google.com> #18Dec 6, 2023 10:04PM

ja...@google.com <ja...@google.com> #19Dec 6, 2023 10:18PM

bo...@mfour.com <bo...@mfour.com> #20Dec 12, 2023 05:54PM

ja...@google.com <ja...@google.com> #21Dec 13, 2023 05:10PM

ja...@google.com <ja...@google.com> #22Dec 14, 2023 05:32PM

co...@protonmail.com <co...@protonmail.com> #23Dec 20, 2023 12:08PM

mi...@fresha.com <mi...@fresha.com> #24Dec 20, 2023 12:13PM

la...@gmail.com <la...@gmail.com> #25Jan 24, 2024 12:18PM

co...@protonmail.com <co...@protonmail.com> #26Jan 25, 2024 03:44AM

ok...@gmail.com <ok...@gmail.com> #27Jan 25, 2024 12:47PM

el...@gmail.com <el...@gmail.com> #28Jan 29, 2024 11:52AM

ch...@gmail.com <ch...@gmail.com> #29Jan 30, 2024 06:54PM

ch...@gmail.com <ch...@gmail.com> #30Jan 31, 2024 02:23PM

ad...@gmail.com <ad...@gmail.com> #31Mar 1, 2024 02:09PM

al...@gmail.com <al...@gmail.com> #32Mar 5, 2024 01:46PM

xa...@google.com <xa...@google.com> #33Mar 8, 2024 02:52AM

so...@google.com <so...@google.com> #34Mar 8, 2024 11:41PM

so...@google.com <so...@google.com> #35Mar 8, 2024 11:41PM

Note

Add comment

Issue metadata