Status Update
Comments
ub...@gmail.com <ub...@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.
uc...@google.com <uc...@google.com>
lf...@google.com <lf...@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> #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>
ra...@google.com <ra...@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
Description
I was trying to report an emulator bug encountered while trying to report a DB Inspector bug, instead I'm reporting a bug about submitting emulator bugs. Kinda sucks, really.
Emulator version 30.0.10-6421526
Click on "Send Feedback" in Help|Emulator Help. As a regular non-Google user I am not allowed to directly create bugs in the "Emulator" bug tracker component.