Status Update
Comments
ku...@google.com <ku...@google.com>
bo...@google.com <bo...@google.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.
bo...@google.com <bo...@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?
ad...@gmail.com <ad...@gmail.com> #4
We have quite some crashes like this:
product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"
tr...@gmail.com <tr...@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
wd...@google.com <wd...@google.com> #6
I suspect EXC_BAD_INSTRUCTION
happens in vImageRotate90_ARGB8888
and vImageScale_ARGB8888
which are used by webcam on MacOS.
tr...@gmail.com <tr...@gmail.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 (
bo...@google.com <bo...@google.com> #9
bo...@google.com <bo...@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.
tr...@gmail.com <tr...@gmail.com> #11
bo...@google.com <bo...@google.com> #12
ad...@gmail.com <ad...@gmail.com> #13
wd...@google.com <wd...@google.com> #14
rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.
wd...@google.com <wd...@google.com>
jo...@gmail.com <jo...@gmail.com> #15
wd...@google.com <wd...@google.com>
bo...@google.com <bo...@google.com> #17
wd...@google.com <wd...@google.com> #18
lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?
ra...@google.com <ra...@google.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
AI-203.7717.56.2031.7935034, JRE 11.0.10+0-b96-7249189x64 JetBrains s.r.o., OS Linux(amd64) v5.15.0-051500-generic, screens 1366.0x768.0
Emulator version:31.1.4
Android SDK platform tools version:31.0.3
Host cpu:12th Gen Intel(R) Core(TM) i5-12600K
Device name:Pixel 5
Emulator with system image android 11 is working properly but Android 12(31) and 12L(32) is not even loading in my PC.
It was working perfectly in my previous PC with Ryzen 3200G processor,So I believe that the issue is with intel 12th gen processor.FYI I'm not using any external GPU.running emulator in cpu.