Emulator performance degraded after updating to version 33.1.1 [270034824]

Verified

Bug

Status Update

No update yet.

Description

nu...@gmail.com

created issue #1

Feb 20, 2023 06:23PM

Hi,

After updating to Emulator v33.1.1 and SDK Platform Tools 34.0.0, emulator performance took a big hit.
It was working ok on previous version, with Apple M1 chip.

I've tried creating a new emulator, but it's a general issue.

Could you give me instructions on how to downgrade to previous version?

```
Build: AI-223.8214.52.2231.9601041, 202302132341,

AI-223.8214.52.2231.9601041, JRE 17.0.6+0-17.0.6b802.4-9586694x64 JetBrains s.r.o., OS Mac OS X(aarch64) v13.2.1, screens 3456.0x2234.0, 3840.0x2160.0; Retina

AS: Giraffe | 2022.3.1 Canary 5
Kotlin plugin: 223-1.7.21-AS7571.182
Android Gradle Plugin: 7.4.1
Gradle: 8.0
Gradle JDK: JetBrains Runtime version 17.0.6
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Source: send_feedback_icon

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.
```

Comments

nu...@gmail.com <nu...@gmail.com> #2Feb 20, 2023 06:41PM

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

r....@gmail.com <r....@gmail.com> #3Feb 21, 2023 03:46PM

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

ha...@google.com <ha...@google.com> Feb 21, 2023 06:53PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Feb 22, 2023 07:48PM

Reassigned to ya...@google.com.

ya...@google.com <ya...@google.com> #4Feb 22, 2023 08:37PM

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?

nu...@gmail.com <nu...@gmail.com> #5Feb 23, 2023 10:04AM

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.

Thu Feb 23 2023 10:04:42 GMT+0000 (Western European Standard Time).png

19 KB

View

Download

ya...@google.com <ya...@google.com> #6Feb 23, 2023 06:22PM

Hi this is the output txt flle

Message last modified on Feb 23, 2023 06:22PM

nu...@gmail.com <nu...@gmail.com> #7Feb 24, 2023 01:44PM

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

Message last modified on Feb 24, 2023 01:46PM

Fri Feb 24 2023 13:41:19 GMT+0000 (Western European Standard Time).png

78 KB

View

Download

ya...@google.com <ya...@google.com> #8Feb 24, 2023 06:27PM

Reassigned to de...@google.com.

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?

ya...@google.com <ya...@google.com> #9Feb 24, 2023 06:28PM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

de...@google.com <de...@google.com> Feb 24, 2023 06:31PM

Accepted by de...@google.com.

ya...@google.com <ya...@google.com> #10Mar 6, 2023 08:00PM

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

jp...@google.com <jp...@google.com> Mar 6, 2023 09:48PM

Status: Duplicate of

271701966

de...@google.com <de...@google.com> #11Mar 6, 2023 09:52PM

Marked as fixed, reassigned to ya...@google.com.

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>

ya...@google.com <ya...@google.com> #12Mar 6, 2023 10:25PM

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.

is...@motorolasolutions.com <is...@motorolasolutions.com> #13May 17, 2023 02:15AM

Does this look related?

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

cs...@google.com <cs...@google.com> #14May 17, 2023 09:06PM

Status: Assigned (reopened)

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.

ya...@google.com <ya...@google.com> #15May 19, 2023 09:23PM

Reassigned to cs...@google.com.

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.

cs...@google.com <cs...@google.com> #16May 19, 2023 09:32PM

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!

Message last modified on May 19, 2023 09:32PM

bo...@google.com <bo...@google.com> #17Nov 13, 2023 04:52PM

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.

cs...@google.com <cs...@google.com> Nov 13, 2023 05:08PM

Status: New

nu...@gmail.com <nu...@gmail.com> #18Nov 13, 2023 05:49PM

Thank you for the update.

bo...@google.com <bo...@google.com> #19Mar 5, 2024 04:44PM

Assigned to bo...@google.com.

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.

nu...@gmail.com <nu...@gmail.com> #20Mar 5, 2024 05:25PM

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!

bo...@google.com <bo...@google.com> Mar 12, 2024 03:22PM

Verified by bo...@google.com.