Memory Safety Violation caught by MTE

Checklist

• I've already searched in existing issues and haven't found a similar problem reported.
• I'm using the latest version of the app
• This error caused the app to crash
• This error is reproducible

Which category best fits this error?

Others

App version

0.15.3

Reproduction steps

I was reading an article from it's foss then the app crashed (but guess its the fault of mte) and i got the following error (i have memory tagging enabled)

when later clicking on the same article it didn't crash again

Crash report

type: crash
userType: full.secondary
package: me.ash.reader:44, targetSdk 34
osVersion: google/tegu/tegu:16/BP4A.251205.006.E1/2026011001:user/release-keys
uid: 1010213 (u:r:untrusted_app:s0:c213,c256,c522,c768)
cmdline: me.ash.reader
processUptime: 581s

signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr 700d6d1ecd2e8d4
threadName: mali-event-hand
MTE: enabled

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (pthread_mutex_unlock+20, pc 932d4)
    /vendor/lib64/egl/libGLES_mali.so (hal::halp::fence_internal::signal_internal()+132, pc 1b38714)
    /vendor/lib64/egl/libGLES_mali.so (hal::halp::signal_fence_cb(void*, bool)+32, pc 1b3fab0)
    /vendor/lib64/egl/libGLES_mali.so (basep_cpu_queue_process+356, pc 1c5a334)
    /vendor/lib64/egl/libGLES_mali.so (basep_process_command_queues+148, pc 1c58134)
    /vendor/lib64/egl/libGLES_mali.so (basep_event_thread+236, pc 1c5625c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+180, pc 91584)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68, pc 813d4)

Start with the supplied crash report, especially the SIGSEGV/MTE details, Android version, app version, and Mali driver backtrace. Try to reproduce the crash while reading the same article with memory tagging enabled; done means establishing whether the app can trigger it or whether the report points only to the device's graphics stack.