Status Update
Comments
nu...@gmail.com <nu...@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.
r....@gmail.com <r....@gmail.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?
ha...@google.com <ha...@google.com>
bo...@google.com <bo...@google.com>
ya...@google.com <ya...@google.com> #4
We have quite some crashes like this:
product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"
nu...@gmail.com <nu...@gmail.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
ya...@google.com <ya...@google.com> #6
I suspect EXC_BAD_INSTRUCTION
happens in vImageRotate90_ARGB8888
and vImageScale_ARGB8888
which are used by webcam on MacOS.
nu...@gmail.com <nu...@gmail.com> #7
ya...@google.com <ya...@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 (
ya...@google.com <ya...@google.com> #9
de...@google.com <de...@google.com>
ya...@google.com <ya...@google.com> #10
We confirmed vImageRotate90...
and vImageScale...
and use what I could find (which is not as efficient as vImage...
ones, we will try to figure out why these functions crash), it does not handle all aspect ratios and resolutions so far (it might crash for different reasons, I will be working on this tomorrow). If anyone wants to try my local build, I can share it.
de...@google.com <de...@google.com> #11
ya...@google.com <ya...@google.com> #12
is...@motorolasolutions.com <is...@motorolasolutions.com> #13
cs...@google.com <cs...@google.com> #14
rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.
cs...@google.com <cs...@google.com> #16
lechun.sk, I shared with you.
bo...@google.com <bo...@google.com> #17
cs...@google.com <cs...@google.com>
nu...@gmail.com <nu...@gmail.com> #18
lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?
nu...@gmail.com <nu...@gmail.com> #20
lechun.sk, unfortunately a bug report will not help here. It would useful to debug issues inside Android. This crash happens outside. There should be a popup window when you start the emulator asking to send a crash report. Maybe it is not available for local builds. The fix is in code review.
Description
After updating to Emulator v33.1.1 and SDK Platform Tools 34.0.0, emulator performance took a big hit.
It was working ok on previous version, with Apple M1 chip.
I've tried creating a new emulator, but it's a general issue.
Could you give me instructions on how to downgrade to previous version?
```
Build: AI-223.8214.52.2231.9601041, 202302132341,
AI-223.8214.52.2231.9601041, JRE 17.0.6+0-17.0.6b802.4-9586694x64 JetBrains s.r.o., OS Mac OS X(aarch64) v13.2.1, screens 3456.0x2234.0, 3840.0x2160.0; Retina
AS: Giraffe | 2022.3.1 Canary 5
Kotlin plugin: 223-1.7.21-AS7571.182
Android Gradle Plugin: 7.4.1
Gradle: 8.0
Gradle JDK: JetBrains Runtime version 17.0.6
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Source: send_feedback_icon
IMPORTANT: Please read
```