IssueTracker

Some more context regarding this issue: https://stackoverflow.com/questions/73417527/android-emulator-initial-network-call-delayed-by-several-seconds/

It's happening on 31.3.10. Reverting to 31.2.10 fixes the problem.

Ignore.

It seems like we can repro the issue with embedded emulator. I used a stopwatch to record how long it takes for Google Sign-In page to load for the first time.

1, stand-alone emulator version (31.3.10): 4 seconds

2, embedded emulator (31.3.10): 15 seconds.

I am using Windows 10 with Intel Core i7-11850H@ 2.50GHz with 32GB RAM.

Ranjit is also able to repro the issue on Windows with Intel CPU. The problem is essentially in the first network connection. I asked Ranjit to help me with bisection mentioned in #3.

Time taken to show the Gmail Sign In page when AVD launched in embedded mode (Used Pixel_4a_API_31)

1. Emulator Version : 31.3.9-8716652   about 17 seconds
2. Emulator Version : 31.3.10-8779787  about 18 seconds
3. Emulator Version : 31.3.10-8803787  about 20 seconds

RE#6 Thanks Ranjit for helping out with bisecting. I think the issue probably existed before I checked in the network related CLs. We will keep bisecting.

Maybe the issue is caused by this CL. Let's try if build (8376731) still has the problem and how does it compare with build (8408262).

According to ranjitkumar@, "It took about 28 seconds with Emulator version 31.3.6-8376731 and It took about 35 seconds for me with Emulator version 31.2.10-8420304" So we are probably chasing down a problem that might just be lingering for very long time.

And our observation is somewhat contradictory to what the user had reported because they believe it's a regression from 31.2.10.