Many in-the-wild SIGABRT crashes in MonodroidRuntime::mono_log_handler

[BioTurboNick]

Description

[split_config.arm64_v8a.apk!libmono-android.release.so] xamarin::android::internal::MonodroidRuntime::mono_log_handler(char const*, char const*, char const*, int, void*)

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 13332 >>> com.NicholasBauer.HemocytometerSidekick.XF <<<

backtrace:
  #00  pc 0x000000000008a074  /apex/com.android.runtime/lib64/bionic/libc.so (abort+180)
  #01  pc 0x00000000000474c8  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmono-android.release.so (xamarin::android::internal::MonodroidRuntime::mono_log_handler(char const*, char const*, char const*, int, void*)+144)
  #02  pc 0x00000000002da93c  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #03  pc 0x00000000002daa68  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #04  pc 0x00000000002daaac  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #05  pc 0x0000000000252f50  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #06  pc 0x0000000000265b18  /data/app/~~KlbFaUHkjJZchSzb2QeIkw==/com.NicholasBauer.HemocytometerSidekick.XF-fwdHMoy4OTEYPi332AyUng==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #07  pc 0x0000000000004f00 

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 16037 >>> com.NicholasBauer.HemocytometerSidekick.XF <<<

backtrace:
  #00  pc 0x000000000008a134  /apex/com.android.runtime/lib64/bionic/libc.so (abort+180)
  #01  pc 0x00000000000474c8  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmono-android.release.so (xamarin::android::internal::MonodroidRuntime::mono_log_handler(char const*, char const*, char const*, int, void*)+144)
  #02  pc 0x00000000002da93c  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #03  pc 0x00000000002daa68  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #04  pc 0x00000000002daaac  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #05  pc 0x0000000000252f50  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #06  pc 0x0000000000265b18  /data/app/~~WTuK0uw8fqhGTqXJ4dFzvw==/com.NicholasBauer.HemocytometerSidekick.XF-my7kHrJ_eskZS0xWk2RPfQ==/split_config.arm64_v8a.apk!libmonosgen-2.0.so
  #07  pc 0x0000000000004f00 

I released my first MAUI version of the app on Christmas.

These are reported in Google Play Console, but not reported in Microsoft AppCenter. I haven't observed this crash in person.

Steps to Reproduce

🤷‍♂️

Link to public reproduction project repository

n/a

Version with bug

7.0 (current)

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android 10 and up

Did you find any workaround?

No response

Relevant log output

No response

[BioTurboNick]

Maybe due to having LLVM turned on: dotnet/android#7588

[rachelkang]

@jonathanpeppers any thoughts on this one?

[jonathanpeppers]

I would recommend turning off either LLVM or profiled AOT until this is resolved:

dotnet/runtime#79910 (comment)

It appears some apps can crash when using both settings at once.

[BioTurboNick]

Ah, thank you!

[ghost]

Hi @BioTurboNick. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.