Running several SentrySdk.CaptureMessage in parallel freezes the MAUI Android app

[dalux-era]

Package

Sentry

.NET Flavor

.NET

.NET Version

9.0.203

OS

Android

OS Version

Android 15

Development Environment

Visual Studio v18.x

SDK Version

5.16.2

Self-Hosted Sentry Version

No response

Workload Versions

android 35.0.39/9.0.100 SDK 9.0.200, VS 17.13.35931.197
aspire 8.2.2/8.0.100 SDK 9.0.200, VS 17.13.35931.197
ios 18.2.9173/9.0.100 SDK 9.0.200, VS 17.13.35931.197
maccatalyst 18.2.9173/9.0.100 SDK 9.0.200, VS 17.13.35931.197
maui-windows 9.0.14/9.0.100 SDK 9.0.200, VS 17.13.35931.197

UseSentry or SentrySdk.Init call

.UseSentry("")

Steps to Reproduce

1. Run SentrySdk.CaptureMessage("Hello") in parallel
2. Use this somewhere in Main thread, like on a button press

 Parallel.Invoke(
     () => SentrySdk.CaptureMessage("Hello"),
     () => SentrySdk.CaptureMessage("Hello"),
     () => SentrySdk.CaptureMessage("Hello"),
     () => SentrySdk.CaptureMessage("Hello"),
     () => SentrySdk.CaptureMessage("Hello")
	);

Expected Result

5 Messages will be reported to Sentry

Actual Result

App freezes and stops responding. This seems like a regression as at least the Sentry.Maui 5.4.0 version works fine with the same code. Please reach out if a sample is needed

[linear]

NET-549

[jamescrosswell]

@dalux-era I'm not able to reproduce this. I tried creating a brand new maui app with this:

	private void OnCounterClicked(object? sender, EventArgs e)
	{
		count++;

		if (count == 1)
			CounterBtn.Text = $"Clicked {count} time";
		else
			CounterBtn.Text = $"Clicked {count} times";

		Parallel.Invoke(
			() => SentrySdk.CaptureMessage("Hello"),
			() => SentrySdk.CaptureMessage("Hello"),
			() => SentrySdk.CaptureMessage("Hello"),
			() => SentrySdk.CaptureMessage("Hello"),
			() => SentrySdk.CaptureMessage("Hello")
		);
		
		SemanticScreenReader.Announce(CounterBtn.Text);
	}

The app runs without issue.

I tried using both dotnet SDK 9.0.203 and 9.0.308 (the most recent 9.x release).

[dalux-era]

Can you try running the same app in release configuration? It might be related to that. @jamescrosswell I tried running the same code you show in release and I could reproduce the bug