IssueTracker

The Android Studio Emulator is intended to be used by app developers to test their app. It is not intended to be used as a device substitute to run arbitrary apps.

Do you know what the app is doing, any graphics related things? I see it runs on swiftshader which crashes sometimes. You could try adding either -gpu swangle_indirect (which will translate OpenGL calls over Vulkan) or -feature -Vulkan (disables Vulkan) to the command line and check if it makes a difference. Do you know if it crashes with a hardware GPU?

attaching the adb logcat logs for the original test

I've tried with -gpu swangle_indirect, I see a different rendering issue there. for -feature -Vulkan, the behaviour is same, attached log (with emulator 32)

I tried the same setup on an m2 mac without the container, didn't see the crash there

Looks like the com.genymobile.scrcpy.CleanUp app is crashing:

...
01-21 04:05:00.168  1407  1596 I SuperpacksForegroundTaskService: SuperpacksForegroundTaskService.finishJob():56 SuperpacksForegroundTaskService.finishJob()
01-21 04:05:00.175   625  1115 W ForegroundServiceTypeLoggerModule: FGS stop call for: 10158 has no types!
01-21 04:05:00.187  5017  5017 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-21 04:05:00.187  5017  5017 F DEBUG   : Build fingerprint: 'google/sdk_gphone64_x86_64/emu64xa:15/AE3A.240806.005/12228598:userdebug/dev-keys'
01-21 04:05:00.187  5017  5017 F DEBUG   : Revision: '0'
01-21 04:05:00.187  5017  5017 F DEBUG   : ABI: 'x86_64'
01-21 04:05:00.187  5017  5017 F DEBUG   : Timestamp: 2025-01-21 04:04:59.867659269+0000
01-21 04:05:00.187  5017  5017 F DEBUG   : Process uptime: 2s
01-21 04:05:00.187  5017  5017 F DEBUG   : Cmdline: app_process / com.genymobile.scrcpy.CleanUp AAAAAP////8CAAAA
01-21 04:05:00.187  5017  5017 F DEBUG   : pid: 4956, tid: 4956, name: main  >>> app_process <<<
01-21 04:05:00.187  5017  5017 F DEBUG   : uid: 2000
01-21 04:05:00.188  5017  5017 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-21 04:05:00.188  5017  5017 F DEBUG   : Abort message: 'No pending exception expected: java.lang.ClassNotFoundException: com.genymobile.scrcpy.CleanUp
01-21 04:05:00.188  5017  5017 F DEBUG   : (Throwable with empty stack trace)'
01-21 04:05:00.188  5017  5017 F DEBUG   :     rax 0000000000000000  rbx 00007ffd3c1f6178  rcx 000079bda9eb3b90  rdx 0000000000000006
01-21 04:05:00.188  5017  5017 F DEBUG   :     r8  000079bb164c9560  r9  000079bb164c9560  r10 00007ffd3c1f6180  r11 0000000000000217
01-21 04:05:00.188  5017  5017 F DEBUG   :     r12 000079bc264c3010  r13 000079bb12e7e861  r14 000000000000135c  r15 000000000000135c
01-21 04:05:00.188  5017  5017 F DEBUG   :     rdi 000000000000135c  rsi 000000000000135c
01-21 04:05:00.188  5017  5017 F DEBUG   :     rbp 0000000000000000  rsp 00007ffd3c1f6170  rip 000079bda9eb3b90
01-21 04:05:00.188  5017  5017 F DEBUG   : 12 total frames
01-21 04:05:00.188  5017  5017 F DEBUG   : backtrace:
01-21 04:05:00.188  5017  5017 F DEBUG   :       #00 pc 000000000005cb90  /apex/com.android.runtime/lib64/bionic/libc.so (abort+192) (BuildId: eb58b4d427279994f00c0e1818477e4f)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #01 pc 000000000087e7c1  /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1537) (BuildId: 62338b1c62e3991543c9b8b8bae2b361)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #02 pc 0000000000015eea  /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+58) (BuildId: 2d7df6e607a8928501c5363a393a3a89)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #03 pc 000000000001540c  /apex/com.android.art/lib64/libbase.so (android::base::LogMessage::~LogMessage()+492) (BuildId: 2d7df6e607a8928501c5363a393a3a89)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #04 pc 00000000008d347c  /apex/com.android.art/lib64/libart.so (art::Thread::AssertNoPendingException() const+1468) (BuildId: 62338b1c62e3991543c9b8b8bae2b361)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #05 pc 000000000049c6f5  /apex/com.android.art/lib64/libart.so (art::ClassLinker::FindClass(art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+53) (BuildId: 62338b1c62e3991543c9b8b8bae2b361)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #06 pc 000000000068b9a3  /apex/com.android.art/lib64/libart.so (art::JNI<false>::FindClass(_JNIEnv*, char const*)+1459) (BuildId: 62338b1c62e3991543c9b8b8bae2b361)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #07 pc 00000000000ed98c  /system/lib64/libandroid_runtime.so (jniRegisterNativeMethods(_JNIEnv*, char const*, JNINativeMethod const*, int) (.llvm.10554325554911834960)+44) (BuildId: 74e467b22a4c3107eac51948743c9977)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #08 pc 00000000000f3191  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::startReg(_JNIEnv*)+129) (BuildId: 74e467b22a4c3107eac51948743c9977)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #09 pc 00000000000f2e83  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vector<android::String8> const&, bool)+627) (BuildId: 74e467b22a4c3107eac51948743c9977)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #10 pc 0000000000004706  /system/bin/app_process64 (main+1638) (BuildId: 2919fb70658f9ff2e805cbbbdd33a33b)
01-21 04:05:00.188  5017  5017 F DEBUG   :       #11 pc 0000000000057c82  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+114) (BuildId: eb58b4d427279994f00c0e1818477e4f)
...

There might be some issues with handling of this error, leading emulator crashes. Can you try creating a new AVD or running the emulator with -wipe-data argument to remove any installed apps and existing data that might be causing the crashes, and let us know if it's working? If not, please send the console logs of the emulator after a crash and the output of of crashreport -u (should give us the crash report id uploaded, to see the crash callstack)?

com.genymobile.scrcpy.CleanUp crashed around 3 mins before the emulator crash, and I have other runs where this app didn't crash.

yeah I'm using -wipe-data in all the runs, my command

~/shared-tools/android-sdk/emulator/emulator -no-boot-anim -no-audio -verbose -read-only -wipe-data -show-kernel

crashreport -u didn't return anything

attached logcat and emulator logs of the latest run on android 15

Also attaching another run on android 13 (emulator version 32.1.12.0) where com.genymobile.scrcpy.CleanUp hadn't crashed

Any update or help in how I can triage this further ?

I tried the same setup on an m2 mac without the container, didn't see the crash there

Macs are arm64, are you only getting crashes on x64 platforms? If that's the case there might be an issue with the NDK translation. If you have source code for the app, adding native x86_64 ABI support may help.

Unfortunately the logs do not show the reason of the crash, can you run run crashreport -u to upload the crashreport after a crash, which should give an id for the report and help us get more information regarding the crashes.

Yes, only see the crash on an x64 machine, though I don't have the app source code. crashreport -u doesn't return anything.

I see, it doesn't sound like it's a graphics emulation related crash and it might be related to one of the libraries the app is using, forwarding to relevant person for further investigation. It would be great if you can provide more details regarding the app, e.g. share a link or apk file.

Macs are arm64, are you only getting crashes on x64 platforms? If that's the case there might be an issue with the NDK translation. If you have source code for the app, adding native x86_64 ABI support may help.

I checked and this app already uses native x86_64 libs (there is no arm64->x86_64 translation involved). So it looks like the problem is actually with x86_64 libs, system or the app. Anyway my team cannot help here.

Also note that test.apk is package org.altruist.PajajExperia, while crash report in comment#6 is for other package com.genymobile.scrcpy.CleanUp. So the crash is either unrelated, or we have wrong apk attached.

Thanks for getting back, the test.apk is correct. As I mentioned in comment#7, the crash of com.genymobile.scrcpy.CleanUp doesn't seem related indeed. Any other suggestion in how I might go about triaging this further ?

I'd suggest contacting to the app developers, so that they can use the source code to pinpoint the crash location, if they can, which would help us fix the issue.

I cannot repro this on our end with the given apk on any platforms, and at this point it's not clear if it's related to the system/environment setup or the app.