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

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

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

Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

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

Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.

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

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

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

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

Android Studio Ladybug Feature Drop | 2024.2.2 RC 1
Android Gradle Plugin 8.8.0-rc01

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 Feb 23, 2023 06:22PM

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

Ucfucuccj

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.

Hyxucyccchccjch

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

Ycucuccjcn

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

Hola mundo

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.

@yahan it will be picked up in the next canary since we are doing snaps!

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

Thanks!

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

Was able to force the emulator to use the host GPU by opening it via the terminal with

./emulator -avd Resizable_API_33 -gpu host

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

Status: Assigned (reopened)

I believe this is still happening in 33.1.10

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

Reassigned to cs...@google.com.

Chris, would you help to send us the verbose log?

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

User on #comment13 should provide it. User was the one who reported this still happening with Play Store images, via Slack communities. I can also try to repro myself.

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

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

do you still have this problem with latest 33.1.20+ ?

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

Status: New

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

If that question is for me, I've tested changing the config.ini back to "hw.gpu.mode=auto" and it appears to be fine. I have 33.1.2.0.

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

Assigned to bo...@google.com.

with 34.1.x stable already, are there still any performance degradation ?

let us know

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

Can confirm the flag is correctly set for new emulators on 34.1.18

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

Verified by bo...@google.com.