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

Have same problem

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

java.util.ConcurrentModificationException
at java.util.WeakHashMap$HashIterator.next(WeakHashMap.java:165)
at androidx.work.impl.utils.WakeLocks.checkWakeLocks(WakeLocks.java:70)
at androidx.work.impl.background.systemalarm.SystemAlarmService.onAllCommandsCompleted(SystemAlarmService.java:69)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.dequeueAndCheckForCompletion(SystemAlarmDispatcher.java:217)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$DequeueAndCheckForCompletion.run(SystemAlarmDispatcher.java:317)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4960)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.system.NativeStart.main(NativeStart.java)

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

https://android-review.googlesource.com/c/platform/frameworks/support/+/857873

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

Will this be released in the next beta? Thanks

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

Yes, it will.

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

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

Seems like it's still not fixed:

Fatal Exception: java.util.ConcurrentModificationException
at java.util.WeakHashMap$HashIterator.next(WeakHashMap.java:165)
at androidx.work.impl.utils.WakeLocks.checkWakeLocks(WakeLocks.java:78)
at androidx.work.impl.background.systemalarm.SystemAlarmService.onAllCommandsCompleted(SystemAlarmService.java:69)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.dequeueAndCheckForCompletion(SystemAlarmDispatcher.java:217)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$DequeueAndCheckForCompletion.run(SystemAlarmDispatcher.java:317)
at android.os.Handler.handleCallback(Handler.java:810)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:189)
at android.app.ActivityThread.main(ActivityThread.java:5532)
at java.lang.reflect.Method.invoke(Method.java)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:950)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:745)

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.

Still happened on beta02, Android 5.0.2

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

Sample app here:

https://issuetracker.google.com/issues/121345393

It's hard to reproduce with SystemAlarmService.onAllCommandsCompleted. Only managed to do it once but it was just luck. The sample app crashes more often though.

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

I meant this url:

https://github.com/rubensousa/WorkManagerConcurrent

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.

Thanks for the bug report and the sample app. Will take another look.

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

Why are you calling a hidden method (WakeLocks#checkWakeLocks) yourself?

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

Just to reproduce the crash faster. I don't call this on the production app.

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

Status: Assigned (reopened)

The fix will be available in beta03:

https://android-review.googlesource.com/c/platform/frameworks/support/+/876992

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

Reassigned to cs...@google.com.

Thanks a lot for fixing it quickly ;)

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

It still seems to happen for me using beta02:

java.util.WeakHashMap$HashIterator.next (WeakHashMap.java:165)
androidx.work.impl.utils.WakeLocks.checkWakeLocks (WakeLocks.java:78)
androidx.work.impl.background.systemalarm.SystemAlarmService.onAllCommandsCompleted (SystemAlarmService.java:69)
androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.dequeueAndCheckForCompletion (SystemAlarmDispatcher.java:217)
androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$DequeueAndCheckForCompletion.run (SystemAlarmDispatcher.java:317)
android.os.Handler.handleCallback (Handler.java:815)
android.os.Handler.dispatchMessage (Handler.java:104)
android.os.Looper.loop (Looper.java:194)
android.app.ActivityThread.main (ActivityThread.java:5624)
java.lang.reflect.Method.invoke (Method.java)
java.lang.reflect.Method.invoke (Method.java:372)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:959)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:754)

Stacktrace is from a X5pro running Android 5.1.

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

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

Another fix will be available in beta03.

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.