Fatal signal 11 from libmonosgen on MAUI Android

Start by reviewing the attached log.txt, log2.txt, log3.txt, and log4.txt alongside the MAUI Android configuration: .NET 10.0-android preview6 on ARM64. Compare the reported fatal signals with the runtime-created page, hidden animated controls, and animation cleanup described in the issue; the investigation is complete when it produces a reproducible case or an actionable diagnosis.

Description

During application run I have some random fatal signal errors (1, 6 and 11 mostly), they occur very rarely and are very hard to reproduce.
I was not able to recreate this issue in a small-sample app and the issue itself occurs on a big project, which has a lot of corporate info, thus I am not able to share it either.

Reproduction Steps

The general info about the application:
This is MAUI Android project.
The app uses a lot of memory and stores up to 3000 objects in a list, during initial load it calculates values from objects in this list and preloads images for these objects.
The app has a screen which contains info about a product, this screen is created at runtime and then stored for a future reuse (it is heavely reused during application use), the screen itself is pretty simple and it's picture could be found below:

Sometimes (very randomly) when app pushes this page to a navigation stack it crashes with fatal signal.

Expected behavior

Page is being pushed and rendered

Actual behavior

Application crashes with fatal signal related to libmonosgen-2.0.so or libmonodroid.so
Logs of crahes are in attachment (app is aw3.apps.remerch)

log.txt
log4.txt
log3.txt
log2.txt

Regression?

It did occur in net9.0-android, but did not test on earlier versions

Known Workarounds

No response

Configuration

.NET: 10.0-android (preview6)
OS: Android
Architecture: ARM64
Is specific: don't know

Other information

Could be useful in solving:
Problematic screen had some hidden controls (not visible at the start), which had animations attached.
Animations were created at runtime, mainly because the length of the animation and parameter length were calculated based on some model values.
On every page load there is a cleanup for the animations attached to these controls.
If this control was not shown for a long time a crash would occur during page load (could be connected to clearing animation state).

I have removed animations and deleted controls, now these controls are created at user's request.
Can not confirm if this has solved the problem, but haven't experienced any new crashes yet (more testing is being done)