[android] `unknown opcode name for 400`, only workaround is UseInterpreter=true

[peter-chapman]

Description

My app crashes on a Pax A920 Pro with:

09-12 15:18:08.578 9672 9672 E : unknown opcode name for 400
--------- beginning of crash
09-12 15:18:08.579 9672 9672 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 9672 (nyname.mauiapp9), pid 9672 (nyname.mauiapp9)
09-12 15:18:08.672 9691 9691 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-12 15:18:08.673 475 475 I /system/bin/tombstoned: received crash request for pid 9672
09-12 15:18:08.674 9691 9691 I crash_dump32: performing dump of process 9672 (target tid = 9672)
09-12 15:18:08.675 9691 9691 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-12 15:18:08.675 9691 9691 F DEBUG : Native Crash TIME: 25743471
09-12 15:18:08.675 9691 9691 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-12 15:18:08.675 9691 9691 F DEBUG : Build fingerprint: 'PAX/A50/A50:8.1.0/OPM2.171019.012/10:user/release-keys'
09-12 15:18:08.675 9691 9691 F DEBUG : Revision: '0'
09-12 15:18:08.675 9691 9691 F DEBUG : ABI: 'arm'
09-12 15:18:08.675 9691 9691 F DEBUG : pid: 9672, tid: 9672, name: nyname.mauiapp9 >>> com.companyname.mauiapp9 <<<
09-12 15:18:08.675 9691 9691 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
09-12 15:18:08.677 9691 9691 F DEBUG : r0 00000000 r1 000025c8 r2 00000006 r3 00000008
09-12 15:18:08.677 9691 9691 F DEBUG : r4 000025c8 r5 000025c8 r6 bea181cc r7 0000010c
09-12 15:18:08.677 9691 9691 F DEBUG : r8 00000000 r9 910200c9 sl 8f3f46e8 fp a286e680
09-12 15:18:08.677 9691 9691 F DEBUG : ip bea181f0 sp bea181b8 lr b0b3dc1b pc b0b37734 cpsr 20000030
09-12 15:18:08.690 9691 9691 F DEBUG : 
09-12 15:18:08.690 9691 9691 F DEBUG : backtrace:
09-12 15:18:08.691 9691 9691 F DEBUG : #00 pc 00019734 /system/lib/libc.so (abort+63)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#1 pc 0001c10b /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x195b000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#2 pc 00094051 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#3 pc 001775e1 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#4 pc 00177569 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#5 pc 0017761f /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#6 pc 001095b3 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#7 pc 00153ef7 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#8 pc 000cf10f /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#9 pc 000d0a71 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#10 pc 000d1963 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.691 9691 9691 F DEBUG : dotnet/maui#11 pc 000d45f3 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.692 9691 9691 F DEBUG : dotnet/maui#12 pc 000d3de7 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.692 9691 9691 F DEBUG : dotnet/maui#13 pc 0004c965 /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.692 9691 9691 F DEBUG : dotnet/maui#14 pc 000453ab /data/app/com.companyname.mauiapp9-LeLjmierad7gzvqYMRibag==/split_config.armeabi_v7a.apk (offset 0x19a2000)
09-12 15:18:08.692 9691 9691 F DEBUG : dotnet/maui#15 pc 00008e54 <anonymous:af430000>

Steps to Reproduce

This can be recreated by creating a fresh MAUI app and renaming the Debug configuration e.g.

Debug.Pax

Version with bug

6.0.486 (current)

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

8.1

Did you find any workaround?

No

Relevant log output

See: #76192 (comment)

[jfversluis]

Does dotnet/maui#9627 have any information that might help you?

Hi @peter-chapman. 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.

[peter-chapman]

That didn't fix it for us.
We are running on a specific piece of Hardware, a PAX A920 Pro POS unit and we haven't been able to recreate the issue on any other HW or emulator but the app works correctly when we use a configuration called Debug and only crashes when we use a configuration called Pax.Debug. It seems likely that there is something in the build system that is picking up the fact that the configuration is called Debug and changing the behaviour, is there anything we can do to determine what this might be?

[iain-mcandrew]

I have the same issue on my Pax A920 Pro. I've attached the adb log.
logcat.txt

In the logs I can see "unknown opcode name for 400"; is this possibly related to this unreseolved bug? dotnet/android#6865

[PureWeen]

@jonathanpeppers is this supported?

[jonathanpeppers]

@iain-mcandrew does the app run on this device in any configuration?

The crash says unknown opcode name for 400, which is the same as here: dotnet/android#6865

The suggestion was to try turning off hot reload / $(UseInterpreter), and I don't think we heard back if that solved anything.

[iain-mcandrew]

@jonathanpeppers The app launches and runs fine on this device if the project Configuration is the default "Debug"; creating a project configuration with a differnt name causes the issue.

Disabling hot reload and fast deployment does not resolve the issue.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[peter-chapman]

@jonathanpeppers
Would it help if you had a device to debug this issue on? We are happy to ship you the device that has the issue to aid with investigation.

[jonathanpeppers]

So both Debug and Release configurations work fine?

Can you build the project with -c Debug -bl:Debug.binlog, -c Release -bl:Release.binlog, and -c Debug.Pax -bl:Debug.Pax.binlog.

Then share these .binlog files?

[iain-mcandrew]

@jonathanpeppers Here are the requested logs. I had to add ".txt" to the end to upload them here.
Debug.binlog.txt
Debug.Pax.binlog.txt
Release.binlog.txt

[jonathanpeppers]

One difference between the Debug & Debug.Pax logs is UseInterpreter.

What if you enable it for every configuration except Release:

<PropertyGroup Condition=" '$(Configuration)' != 'Release' ">
 <UseInterpreter>true</UseInterpreter>
</PropertyGroup>

Does that solve anything?

[iain-mcandrew]

Setting UseInterpreter to true does seem to fix the Debug.Pax build!
To answer your previous question, it seems Release doesn't work either. Enabling UseInterpreter for release build doesn't seem to fix it though.

[jonathanpeppers]

@iain-mcandrew does Release work if you do:

<PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
 <RunAOTCompilation>true</RunAOTCompilation>
 <AndroidEnableProfiledAot>false</AndroidEnableProfiledAot>
</PropertyGroup>

This will AOT the entire app, instead of using Profiled AOT (the default).

It might be there is an issue with the JIT on a specific device? This is a "PAX A920 Pro POS unit"?