[Xamarin.Android] Assertion `tramp-arm64.c:52, condition '((ins >> 24) & 0x1f) == 0x10' not met`

[jeromelaban]

Android application type

Classic Xamarin.Android (MonoAndroid12.0, etc.)

Affected platform version

VS 2022 of Azure Devops agents 20220828.1

Description

Using Profiled AOT, the following crash happens when running on device (A surface Duo 2 here). Note that the issue does not happen when using "normal" AOT without a profile. I'm not able to reproduce on net6.0 because there are no easy steps to create a profile.

09-06 22:33:33.042  8303  8303 I crash_dump64: performing dump of process 8271 (target tid = 8271)
09-06 22:33:33.045  8303  8303 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-06 22:33:33.045  8303  8303 F DEBUG   : Build fingerprint: 'surface/duo2/duo2:11/2022.519.47/202205190047:user/release-keys'
09-06 22:33:33.045  8303  8303 F DEBUG   : Revision: '0'
09-06 22:33:33.045  8303  8303 F DEBUG   : ABI: 'arm64'
09-06 22:33:33.045  8303  8303 F DEBUG   : Timestamp: 2022-09-06 22:33:33-0400
09-06 22:33:33.045  8303  8303 F DEBUG   : pid: 8271, tid: 8271, name: ive.uno.ui.demo  >>> com.nventive.uno.ui.demo <<<
09-06 22:33:33.045  8303  8303 F DEBUG   : uid: 10308
09-06 22:33:33.045  8303  8303 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
09-06 22:33:33.046  8303  8303 F DEBUG   : Abort message: '* Assertion at /Users/builder/jenkins/workspace/archive-mono/2020-02/android/release/mono/mini/tramp-arm64.c:52, condition `((ins >> 24) & 0x1f) == 0x10' not met
09-06 22:33:33.046  8303  8303 F DEBUG   : '
09-06 22:33:33.046  8303  8303 F DEBUG   :     x0  0000000000000000  x1  000000000000204f  x2  0000000000000006  x3  0000007fccd03f00
09-06 22:33:33.046  8303  8303 F DEBUG   :     x4  fefefefefefefeff  x5  fefefefefefefeff  x6  fefefefefefefeff  x7  7f7f7f7f7f7f7f7f
09-06 22:33:33.046  8303  8303 F DEBUG   :     x8  00000000000000f0  x9  2e64e12967d126ae  x10 0000000000000000  x11 ffffffc0fffffbdf
09-06 22:33:33.046  8303  8303 F DEBUG   :     x12 0000000000000001  x13 00000000000000a3  x14 0000c8057b4e42db  x15 0000000034155555
09-06 22:33:33.046  8303  8303 F DEBUG   :     x16 0000007c8968dc80  x17 0000007c8966f870  x18 0000000000000008  x19 000000000000204f
09-06 22:33:33.046  8303  8303 F DEBUG   :     x20 000000000000204f  x21 00000000ffffffff  x22 000000798a6a0320  x23 000000798a7de480
09-06 22:33:33.046  8303  8303 F DEBUG   :     x24 b400007ae68b9bd0  x25 0000007990511000  x26 000000798a6a02e8  x27 0000000000000000
09-06 22:33:33.046  8303  8303 F DEBUG   :     x28 0000007c8be69000  x29 0000007fccd03f80
09-06 22:33:33.046  8303  8303 F DEBUG   :     lr  0000007c896232a0  sp  0000007fccd03ee0  pc  0000007c896232cc  pst 0000000000001000
09-06 22:33:33.046  8303  8303 F DEBUG   : backtrace:
09-06 22:33:33.046  8303  8303 F DEBUG   :       #00 pc 000000000004e2cc  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
09-06 22:33:33.046  8303  8303 F DEBUG   :       #01 pc 000000000028e850  /data/app/~~6hfhmZOL2T6K4N24pAS5VQ==/com.nventive.uno.ui.demo-ErE4OrB5kZmmdiQVwrImHw==/lib/arm64/libmonosgen-2.0.so (monoeg_assert_abort+24)
09-06 22:33:33.126   854   854 E tombstoned: Tombstone written to: /data/tombstones/tombstone_28

Steps to Reproduce

1. checkout unoplatform/Uno.Gallery@bca93dd
2. Build Uno.Gallery/Uno.Gallery.Droid/Uno.Gallery.Droid.csproj in Release
3. Run on device.

Did you find any workaround?

• Using non-profiled AOT
• Disabling LLVM ([Xamarin.Android] Assertion tramp-arm64.c:52, condition '((ins >> 24) & 0x1f) == 0x10' not met #7352 (comment))

Relevant log output

No response

[dellis1972]

@grendello do we need any additional info to investigate this?

[grendello]

@dellis1972 someone from the Runtime team needs to look at it, however a full log would be a good thing to have.

@jeromelaban would you mind recording and attaching the crash log using instructions below?

$ adb shell setprop debug.mono.log default,assembly,mono_log_mask=all,mono_log_level=debug
$ adb logcat -G 16M
$ adb logcat -c
# Run the app here and after it crashes, do
$ adb logcat -d > log.txt

Hi @jeromelaban. We have added the "need-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.

[jeromelaban]

Here's the log:
log.txt