Status Update
Comments
db...@gmail.com <db...@gmail.com> #2
Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:
cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP
if there is a crash report to send, please send it and attach the report id.
vi...@google.com <vi...@google.com>
bo...@google.com <bo...@google.com>
wd...@google.com <wd...@google.com> #3
We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001
and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?
wd...@google.com <wd...@google.com>
wd...@google.com <wd...@google.com> #4
We have quite some crashes like this:
product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"
wd...@google.com <wd...@google.com> #5
The most of crashes happen here:
vVertical_Scale_ARGB_8888_Accelerate
vImageVerticalShear_ARGB8888
vImageVerticalShear_ARGB8888
vImageScale_ARGB8888
vRotateClockwise270Degree_ARGB8888_Accelerate2
vRotate_90_ARGB_8888_270Degree_Accelerate2
wd...@google.com <wd...@google.com>
db...@gmail.com <db...@gmail.com> #6
I suspect EXC_BAD_INSTRUCTION
happens in vImageRotate90_ARGB8888
and vImageScale_ARGB8888
which are used by webcam on MacOS.
wd...@google.com <wd...@google.com> #7
wd...@google.com <wd...@google.com> #8
Hi rforzani22, I am sorry for this experience. This bug is my top priority. We expect a fix to be merged within a week. You should be able to download a build directly from our build server (
Description
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.14-9322596 HAXM / KVM Version: HAXM 7.6.5
Android SDK Tools: 26.1.1
Host Operating System: Windows 10 Pro
CPU Manufacturer: Intel CPU Virtualization is supported 64-bit CPU
RAM: 16327 MB
GPU: GPU #1 Make: 1002 Model: AMD Radeon HD 7570 Device ID: 675d
Build Fingerprint:
AVD Details: Name: Pixel_2_API_33_2 CPU/ABI: x86_64 Path: C:\Users\Doron.android\avd\Pixel_2_API_33_2.avd Target: google_apis_playstore [Google Play] (API level 33) Skin: pixel_2 SD Card: 512M AvdId: Pixel_2_API_33_2 PlayStore.enabled: true avd.ini.displayname: Pixel 2 API 33 2 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\x86_64
runtime.network.latency: none runtime.network.speed: full showDeviceFrame: yes skin.dynamic: yes tag.display: Google Play tag.id: google_apis_playstore vm.heapSize: 228
Steps to Reproduce Bug:
Write Hebrew characters when sending a message - the message is not sent. Same happens if sent programmatically from another app. The happens on API 33 but not on API 29.
Expected Behavior:
Observed Behavior: