IssueTracker

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.

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?

We have quite some crashes like this:

product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"

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

I suspect EXC_BAD_INSTRUCTION happens in vImageRotate90_ARGB8888 and vImageScale_ARGB8888 which are used by webcam on MacOS.

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 (https://ci.android.com/builds/branches/aosp-emu-master-dev/grid) once the fix is merged. The release process will take some additional time.

We confirmed #comment6. I removed 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.

rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.

lechun.sk, I shared with you.

lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?

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.

Do you mind trying API34? We have a new camera HAL there.

This is the emulator build on our build server:

https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip

But it lags

yes, it does, because our rotation is not as efficient as vImageRotate90_ARGB8888.

and then crashes

I can't repro it with a build-in camera in my laptop. What camera do you use? Do you see a crash upload dialog to upload it (please share the ID if you have one)?

I can't repro it with a build-in camera in my laptop. What camera do you use?

You can use OBS Studio or XSplit VCam to create a virtual webcam, or you can purchase any Logitech camera, both of which should cause a crash.

Do you see a crash upload dialog to upload it (please share the ID if you have one)?

The dialog doesn't appear at all.

You can use OBS Studio

No crash, see the emulator screen recording. What resolution do you use in OBS Studio?

What resolution do you use in OBS Studio?

1280 * 720. By the way, I'm using mac mini 2023(M2).

• simulator version: sdk-repo-darwin_aarch64-emulator-10914596
• log(only four lines)

VERBOSE | Timed out with running command |/Users/user/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am broadcast -a com.android.emulator.multidisplay.START -n com.android.emulator.multidisplay/.MultiDisplayServiceReceiver |
[54176:8959974:20231007,XXXXXX.766822:WARNING in_range_cast.h:38] value -634136515 out of range
[54176:8959974:20231007,XXXXXX.823661:WARNING crash_report_exception_handler.cc:235] UniversalExceptionRaise: (os/kern) failure (5)
[1]    54174 illegal hardware instruction  emulator -avd Test_Pixel_5_API_31 -verbose

1280 * 720

Still cannot reproduce, unfortunately. I put 60FPS to match your screenshot. I also tried 720*1280, it even crops correctly.

I'm using mac mini 2023(M2)

MacBook 2021 (M1 Max).

Unfortunately, I don't have an update as it works for me (somewhat slow, yes).

Hi

In case anybody is still experimenting a crash with https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip , please consider running just after the crash the command

• crashreport -l to see if a local crash has been created
• crashreport -u to upload the crash (if any). It will give a crash report-id, and please enter the crashid as a comment of this bug. It will help us if you can also say what you were doing during the crash, and if you were using a specific webcam

crashreport being part of the zipfile sdk-repo-darwin_aarch64-emulator-10914596.zip

We were able to reproduce the crashes on different MacOS running Sonoma before the fix in 10914596, but since the fix, the emulator is not crashing anymore in our tests on Sonoma.

Thanks

You want to download the file (sdk-repo-darwin_aarch64-emulator-10914596.zip) and

xattr -d com.apple.quarantine sdk-repo-darwin_aarch64-emulator-10914596.zip

then unzip it.

So how do I open it?

Start it from the console, e.g. ANDROID_SDK_ROOT=/Users/rforzani22/Library/Android/sdk ./emulator -avd YOUR_AVD -wipe-data -no-snapshot -camera-back webcam0

Hi skergx, thank you for the feedback. What CPU do you run on?

We are working on a better patch (the performance should be about as before and should also work on non-Max CPUs as we see here), the build should be available today-tomorrow.

I shared my local build with our next patch to fix this issue.

This is our second version:

https://ci.android.com/builds/submitted/10937044/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10937044.zip

Hi clerici.m89, thank you for the update. Could you please try (our first fix):

https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip

Hi Andi, the Android Emulator is released independently from the Android Studio. The 32.x.x version is EOL, 33.x.x will be promoted to stable soon and the webcam fixes will be available there.

also the image has different size as before, at least with obs before sonoma i was seeing a cropped image out of the 1280x720 but now i can see it full size on the emulator screen.

In the first fix there is no scale function, I crop and put black everywhere I have no pixels for. When we have the scale function, we crop a smaller image and resize to fill all requested pixels.

Hi Andi, thank you for reporting this. I think this is a different problem here as 10914596 does not change anything related to opening the device and 10937044 probably missed even more around this case.