Assertion when stepping over breakpoint

[rolfbjarne]

Description

The app crashes with an assertion when stepping over a breakpoint.

Ref: mono/mono#19899

Reproduction Steps

Test project: https://github.com/user-attachments/files/17809842/debugger_assert.zip

Steps to reproduce:

1. Place a breakpoint at AppDelegate.cs:34
2. Run application with debugger - I used VS Code.
3. Step-over from breakpoint

Expected behavior

No crash.

Actual behavior

Result: app crashes with:

error: * Assertion at /Users/runner/work/1/s/src/mono/mono/mini/mini-arm64.c:6876, condition `native_offset % 4 == 0' not met

Crash report: https://gist.github.com/rolfbjarne/0419d1637fd7176221aed5c569f39220
Debug console output: https://gist.github.com/rolfbjarne/53fcc11a7c15485cbc1301ffb6e004e4

Regression?

No response

Known Workarounds

No response

Configuration

$ dotnet --info
.NET SDK:
 Version:           9.0.100
 Commit:            59db016f11
 Workload version:  9.0.100-manifests.633e1062
 MSBuild version:   17.12.7+5b8665660

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  14.7
 OS Platform: Darwin
 RID:         osx-arm64
 Base Path:   /usr/local/share/dotnet/sdk/9.0.100/

.NET workloads installed:
 [macos]
   Installation Source: SDK 9.0.100
   Manifest Version:    15.0.9617/9.0.100
   Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.sdk.macos/15.0.9617/WorkloadManifest.json
   Install Type:        FileBased

 [maui-ios]
   Installation Source: SDK 9.0.100
   Manifest Version:    9.0.10/9.0.100
   Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.sdk.maui/9.0.10/WorkloadManifest.json
   Install Type:        FileBased

 [ios]
   Installation Source: SDK 9.0.100
   Manifest Version:    18.0.9617/9.0.100
   Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.sdk.ios/18.0.9617/WorkloadManifest.json
   Install Type:        FileBased

 [maccatalyst]
   Installation Source: SDK 9.0.100
   Manifest Version:    18.0.9617/9.0.100
   Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.sdk.maccatalyst/18.0.9617/WorkloadManifest.json
   Install Type:        FileBased

 [android]
   Installation Source: SDK 9.0.100
   Manifest Version:    35.0.7/9.0.100
   Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.sdk.android/35.0.7/WorkloadManifest.json
   Install Type:        FileBased

Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.0
  Architecture: arm64
  Commit:       9d5a6a9aa4

.NET SDKs installed:
  8.0.304 [/usr/local/share/dotnet/sdk]
  8.0.402 [/usr/local/share/dotnet/sdk]
  9.0.100 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.8 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.0-rc.2.24474.3 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Other information

No response

[dotnet-policy-service]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

[mlancione]

Any update on this issue? I see that the .NET 10 milestone was assigned. Does this mean we should expect that the issue will only be addressed in .NET 10?

[ppereira-serviceonsites]

This caused me a headache with Apple submission as it failed on an iPad test of theirs.

I did some testing and found that when I downgraded the following from Version 9.0.3 to 9.0.2 the problem went away:

Microsoft.AspNetCore.Components.Authorization
Microsoft.AspNetCore.Components.WebAssembly.Authentication
Microsoft.Extensions.Caching.Memory
Microsoft.Extensions.Hosting
Microsoft.Extensions.Http.Polly
Microsoft.Extensions.Localization
Microsoft.Extensions.Logging.Debug

Not sure which is the actual culprit although I suspect Polly and Localization are probably not... but at this point, they are all matching each other and seem to fix the problem.

[mlancione]

Any updates on this issue?

[mlancione]

Any progress on getting this included in .NET 10?