IssueTracker

Update: I was able to downgrade to 32.1.10 and I can confirm it's smooth again. The issue is indeed in emulator version 33.1.1

It's happening to me too and I also confirm that reverting to 32.1.10 fixes the issue.

We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.

Hi,

would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?

Hi,

I'm currently not able to change this option, it is greyed out.

Hi,

there are 2 ways to set it:

1. use a google_apis image (instead of google_apis_playstore). it will re-enable the option.
2. go to your avd folder (usually located in ~/.android/avd/your_avd_name.avd/), open config.ini and hardware-qemu.ini, then modify those lines:

hw.gpu.enabled=yes
hw.gpu.mode=host

Hi,

Yes, option 2 fixes the issue (which also persists on 33.1.2 btw). Even though I get a warning when I start the emulator (see attachments).

Will this option be enabled "out of the box" in a future version?

Hi,

we suspect a bug in gpu detection logic on Mac M1, and will try to address it in upcoming releases.

Hi Devki,

would you help to cp aosp/2451107 to next stable and canary releases? Thank you!

Hi Devki,

Could we cherry-pick it to canary release as well? Thanks!

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

Thanks!

do you still have this problem with latest 33.1.20+ ?

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.

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

let us know

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

#19, also in general crash rate as a metric is not a useful one here. We know once these devices get into this state, its hard to recover.
Can you take a look at your crashes to see the total number of users affected ? It will be useful to know what devices they are on as well.

Sorry for spam this issue, but ther eis just 6 starred people, so I think it's ok.

Could you please look at: https://issuetracker.google.com/issues/63622293 (200 starred people, for a 2 years).
And some next info in https://issuetracker.google.com/issues/115560697 60 starred people for a year).

We use now 2.1.0-alpha03 and this crash (100 jobs) looks fixed for us. But https://issuetracker.google.com/issues/63622293 still happen on almost all platforms and it's not possible to workaround it, intead of this one which was possible workaround by cancelling all jobs after start app.

Thanks a lot

You posted screenshots of your build.gradle file and it's using WorkManager 2.1.0-alpha03. (https://issuetracker.google.com/issues//63622293)

I am not sure i understand why you are conflating WorkManager and JobIntentService here.

The crash in JobIntentService and your usage of 2.1.0-alpha03 are not related at all.

I'm sorry, I and some next pelople think, that JobIntentService is related to Workmanager, because before WorkManager we used JobScheduler and JobIntentService... etc, still have mess around jobs and notifications and background services...

We believe we're seeing 1M crashes a day from this problem. Would be great to get this fixed quickly.

#26: It would be great to get some more details as we believe the problem has been addressed (this bug is marked as fixed).  What version of WorkManager are you using?  Can you give more details?

Hi aarmstro@

Which version of WorkManager are you using. This bug has been marked fixed for around ~3 weeks. Are you using the new beta ?

I believe we are not yet using the beta (since we generally try to run only stable libraries for our production app). We'll investigate the fix there though. Do you feel confident that the beta is stable enough for large apps to use?

Google apps usually take drops from HEAD all the time. So I would say yes.

 If you are uncomfortable then you can always try using it in a beta
rollout of the app.

On Thu, Jun 20, 2019 at 5:45 PM <buganizer-system@google.com> wrote: