After the emulator update, the network speed is slow [243053479]

Verified

Bug

Status Update

No update yet.

Description

a7...@gmail.com

created issue #1

Aug 19, 2022 02:56PM

Please Read:

https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: Unknown

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.10-8807927
HAXM / KVM Version: gvm 65544.0.0

Android SDK Tools: 26.1.1

Host Operating System: Windows 10 Enterprise LTSC 2021

CPU Manufacturer: AMD CPU
Virtualization is supported
64-bit CPU

RAM: 32692 MB

GPU: GPU #1
Make: 1002
Model: Radeon (TM) RX 480 Graphics
Device ID: 67df

Build Fingerprint:

AVD Details: Name: Pixel_5_API_30
CPU/ABI: x86
Path: C:\Users\Tom\.android\avd\Pixel_5_API_30.avd
Target: google_apis [Google APIs] (API level 30)
Skin: pixel_4
SD Card: 512M
AvdId: Pixel_5_API_30
PlayStore.enabled: false
avd.ini.displayname: Pixel 5 API 30
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:3274126e0242a0d86339850416b0ce34
hw.device.manufacturer: Google

hw.device.name: pixel_5
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2340
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSize: 1536
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images\android-30\google_apis\x86\
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google APIs

tag.id: google_apis
vm.heapSize: 256

Steps to Reproduce Bug:network speed is too slow
Expected Behavior:

Observed Behavior:

Comments

ya...@google.com <ya...@google.com> Aug 19, 2022 05:06PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Aug 19, 2022 05:07PM

Reassigned to wd...@google.com.

r....@gmail.com <r....@gmail.com> #2Aug 20, 2022 04:37PM

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

wd...@google.com <wd...@google.com> Aug 30, 2022 06:11PM

Accepted by wd...@google.com.

wd...@google.com <wd...@google.com> #3Aug 31, 2022 04:30PM

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.

Message last modified on Aug 31, 2022 08:18PM

wd...@google.com <wd...@google.com> #4Aug 31, 2022 05:51PM

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.

Message last modified on Aug 31, 2022 06:06PM

wd...@google.com <wd...@google.com> #5Aug 31, 2022 06:21PM

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!

Message last modified on Aug 31, 2022 07:50PM

ra...@google.com <ra...@google.com> #6Aug 31, 2022 07:17PM

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!

wd...@google.com <wd...@google.com> #7Aug 31, 2022 07:35PM

Ucfucuccj

wd...@google.com <wd...@google.com> #8Aug 31, 2022 07:41PM

Hyxucyccchccjch

wd...@google.com <wd...@google.com> #9Aug 31, 2022 10:36PM

Ycucuccjcn

Message last modified on Sep 1, 2022 02:28PM

wd...@google.com <wd...@google.com> #10Sep 6, 2022 03:17PM

Hola mundo

wd...@google.com <wd...@google.com> Sep 9, 2022 08:17PM

Marked as fixed.

wd...@google.com <wd...@google.com> #11Sep 12, 2022 07:49PM

@ranjitkumar

Here is the verification steps for this bug.

Host Operating System: Windows 10

Set up: Disable ipv6 manually in Windows by referring to the link. To confirm that ipv6 is not in use, go to http://test-ipv4.com/ and make sure that ipv6 is not supported.

Repro step: 1, Create AVD with API 31 and wipe data before each run.

2, Run AVD and make sure it is cold boot.

3, Immediately after the device boot completes, go to Gmail or Google and try to load the Google Sign In page.

4, Google Sign In page should take more than 1 minute to load for the buggy version (32.3.10). Google Sign in page should take less than 20 seconds for the new version (with fix in CL to load.

Message last modified on Sep 12, 2022 07:49PM

ra...@google.com <ra...@google.com> #12Sep 12, 2022 08:47PM

Thanks for the steps Weilun.

When I tried to load the sign in page after disabling the ipV6 manually it takes more than 2 minutes for the sign in page to show up with stable Emulator 31.3.10.

I will verify the fix in the upcoming Emulator build.

ra...@google.com <ra...@google.com> #13Sep 13, 2022 09:51PM

Verified by ra...@google.com.

This bug has been verified as fixed with the latest Emulator build that is shared with QA.

It takes about 20 seconds for the Gmail sign in page to show up on AVD(Pixel_4a_API_31) with Emulator 31.3.11-9032202 using ipv4 in stand alone mode.

OS : Windows 10

jb...@gmail.com <jb...@gmail.com> #14Oct 15, 2022 01:45PM

128RM 8