Skip to content

[Mono] [Android] Assertion in mono_static_field_get_addr during app startup after dotnet/dotnet update #131760

Description

@jonathanpeppers

Regression

dotnet/android PR #12267 updates dependencies from dotnet/dotnet. The resulting Android Mono runtime test lane now aborts during startup, before any tests run.

Failure

CI build: 1537503

* Assertion at /__w/1/s/src/runtime/src/mono/mono/metadata/object.c:3109,
  condition `field->type->attrs & FIELD_ATTRIBUTE_STATIC' not met

The process then aborts with SIGABRT while initializing the Android test app:

F monodroid: Abort at mono-log-adapter.cc:46:3
F libc: Fatal signal 6 (SIGABRT)
Process Mono.Android.NET_Tests exited due to signal 6

The failure occurs after loading Mono.Android.NET-Tests, Mono.Android, Java.Interop, and Mono.Android.Runtime, and immediately before test execution.

Dependency range

The Android PR advances the dotnet/dotnet dependency from:

  • cb8306a63c5cf24e9381108a3a9eb58907fd0f60
  • to 5da2de22f7c6e2ebe7ed4c16c614b00183145d3c

dotnet/dotnet diff:

dotnet/dotnet@cb8306a...5da2de2

The corresponding dotnet/runtime source range extracted from the dotnet/dotnet codeflow updates is:

dbb2178...cf81048

The final codeflow update identifying cf81048c496a54cca41f960e70bf3981d1d33e72 is dotnet/dotnet#8075.

Might be related

This may be related to dotnet/runtime #131219, commit a7bb6dfe4ab5ba1804be80698cf138a65e9c0370, which changes Mono IMT slot construction in mono/metadata/object.c.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions