Memory Tagging on all app crashes. We need a way to detect these?

GazelleInitial

Briefly. I've enabled MTE memory tagging on all third party apps now.

I have however noticed 1-2 apps force closing when it's enabled and it stops when disabled. There is no warnings or errors.
It just force closes. Not an issue, they;re likely not supported so i'll disable it but it would be good if GOS could somehow detect this and show a toast/notification letting us know.

Similar to when a hardened_malloc detects an error and crashes. I know it's not the same, it's more an unsupported app but it will really affect the experience of people phone usage when this is enabled for all apps by default which is the future plan.

Thanks.

Apps so far: Meshcore, Whataspp, ClassDojo.

Cellobright

GazelleInitial It does, the notification will say "Memory tagging detected an error in APPNAME," but sometimes the app crashes with a reason not related to memory tagging but rather potentially a null pointer reference from not being able to fetch data due to memory tagging (and therefore no notification), and even if an app has a memory tagging error it may handle it gracefully and not crash.

de0u

GazelleInitial [...] Meshcore [...]

A while ago I installed the then-current MeshCore app on a device without MTE. Very reliably, it slowed down and suddenly exited a minute or so after any repeater administration, but not otherwise.

I think the app is just buggy.