Status Update
No update yet.
Comments
da...@google.com
ap...@google.com
Please Read:
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.15-9456632 HAXM / KVM Version: HVF 13.0.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.0.1
CPU Manufacturer: Other CPU: 64-bit CPU
RAM: 32768 MB
GPU:
Build Fingerprint:
AVD Details: Name: Pixel_2_API_33 CPU/ABI: arm64 Path: /.android/avd/Pixel_2_API_33.avd Target: google_apis_playstore [Google Play] (API level 33) Skin: 1080x1920 SD Card: 512M AvdId: Pixel_2_API_33 PlayStore.enabled: true avd.ini.displayname: Pixel 2 API 33 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:55acbc835978f326788ed66a5cd4c9a7 hw.device.manufacturer: Google hw.device.name: pixel_2 hw.gps: yes hw.gpu.enabled: yes hw.gpu.mode: auto hw.initialOrientation: Portrait hw.keyboard: yes hw.lcd.density: 420 hw.lcd.height: 1920 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-33/google_apis_playstore/arm64-v8a/ runtime.network.latency: none runtime.network.speed: full showDeviceFrame: no skin.dynamic: yes skin.path.backup: /Users/***/Development/Android/skins/pixel_2 tag.display: Google Play tag.id: google_apis_playstore vm.heapSize: 228
Steps to Reproduce Bug:
Install Android Studio Eel
Create an emulator with API 23
Run the emulator from AS
The emulator started from Android studio can't resolve any URLs.
Android Studio: Android Studio Electric Eel | 2022.1.1 Build #AI-221.6008.13.2211.9477386, built on January 11, 2023 Runtime version: 11.0.15+0-b2043.56-8887301 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 13.0.1 GC: G1 Young Generation, G1 Old Generation Memory: 5128M Cores: 10 Registry: external.system.auto.import.disabled=true ide.text.editor.with.preview.show.floating.toolbar=false ide.instant.shutdown=false ide.balloon.shadow.size=0
Non-Bundled Plugins: org.toml.lang (221.6008.15) com.intellij.marketplace (221.6008.18) Key Promoter X (2022.2) mobi.hsz.idea.gitignore (4.4.0) com.developerphil.adbidea (1.6.8) izhangzhihao.rainbow.brackets (2023.1.1-ij)
What helps is to start the emulator from the command line -netdelay none -netspeed full -dns-server '2001:4860:4860::8844,2001:4860:4860::8888,8.8.8.8,8.8.4.4'
Expected Behavior:
Network works on emulator started from AS.
Observed Behavior:
Emualtor started from AS either "in-window" or in a separate window can't set up a network. Though it looks like emulators with API 23,24,25 work fine.
Description
Version used: 2.0.0
Devices/Android versions reproduced on: Any
We recently started seeing a lot of lock contention upon subscription to Observables provided by Room. At first we thought that the problem was caused by `syncTriggers` doing DB work on the main thread (a known issue here:
It seems that the close lock is unintentionally being used to obtain an exclusive lock on the entire database, blocking any other subscriptions while there is either another subscription happening at the same time or the refresh runnable is running. I'm not sure why the protection against closing is required in the first place, but maybe a `ReentrantReadWriteLock` could accomplish the intended goal without the exclusiveness.