[ViewPager2] Potential Race condition for gcFragments and Grace period (FragmentTransaction::addToBackStack) [139095195]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Aug 8, 2019 03:38AM

When switching in and out of a Fragment containing ViewPager2 fast, After exactly 10 Seconds after returning to the ViewPager2 Fragment (GRACE_WINDOW_TIME_MS), the current page disappears.

Creating Sample app to verify, but in case this is already a known issue

Comments

[Deleted User] <[Deleted User]> #2Aug 8, 2019 06:21AM

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

[Deleted User] <[Deleted User]> #3Aug 8, 2019 06:25AM

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.

jg...@google.com <jg...@google.com> Aug 8, 2019 11:26AM

Assigned to jg...@google.com.

[Deleted User] <[Deleted User]> #4Aug 8, 2019 04:33PM

Hi,

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

jg...@google.com <jg...@google.com> #5Aug 9, 2019 01:30PM

Hi,

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

jg...@google.com <jg...@google.com> #6Aug 15, 2019 09:52PM

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

jg...@google.com <jg...@google.com> #7Aug 15, 2019 10:01PM

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?

jg...@google.com <jg...@google.com> #8Aug 15, 2019 10:02PM

Hi,

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

[Deleted User] <[Deleted User]> #9Aug 15, 2019 10:19PM

Hi Devki,

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

[Deleted User] <[Deleted User]> #10Aug 15, 2019 10:21PM

Hi Devki,

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

jg...@google.com <jg...@google.com> #11Aug 16, 2019 02:24PM

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

[Deleted User] <[Deleted User]> #12Aug 19, 2019 07:09PM

Thanks!

jg...@google.com <jg...@google.com> Aug 22, 2019 07:55PM

Accepted by jg...@google.com.

jg...@google.com <jg...@google.com> #13Aug 22, 2019 09:25PM

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

[Deleted User] <[Deleted User]> #14Aug 23, 2019 06:56PM

I believe this is still happening in 33.1.10

[Deleted User] <[Deleted User]> #15Aug 23, 2019 07:00PM

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

ap...@google.com <ap...@google.com> #16Aug 27, 2019 06:54PM

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.

ap...@google.com <ap...@google.com> #17Aug 27, 2019 06:54PM

do you still have this problem with latest 33.1.20+ ?

jg...@google.com <jg...@google.com> #18Sep 5, 2019 08:14PM

Marked as fixed.

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.