Debugging a native SIGSEGV crash

I recently updated my podcast app to Flutter 3.29.x. When running a release build on Android and streaming audio in the background, the app crashes after a few minutes. Looking at the logs I can see a SIGSEGV fault as shown by this snippet:

04-19 00:36:58.468 15525 15545 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-19 00:36:58.468 15525 15545 F DEBUG   : Build fingerprint: 'google/oriole/oriole:15/BP1A.250305.019/13003188:user/release-keys'
04-19 00:36:58.468 15525 15545 F DEBUG   : Revision: 'MP1.0'
04-19 00:36:58.468 15525 15545 F DEBUG   : ABI: 'arm64'
04-19 00:36:58.468 15525 15545 F DEBUG   : Timestamp: 2025-04-19 00:34:30.261352732+0100
04-19 00:36:58.468 15525 15545 F DEBUG   : Process uptime: 7873s
04-19 00:36:58.468 15525 15545 F DEBUG   : Cmdline: com.android.chrome:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:3
04-19 00:36:58.468 15525 15545 F DEBUG   : pid: 15525, tid: 15545, name: binder:15525_2  >>> com.android.chrome:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:3 <<<
04-19 00:36:58.468 15525 15545 F DEBUG   : uid: 90003
04-19 00:36:58.468 15525 15545 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
04-19 00:36:58.468 15525 15545 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr --------
04-19 00:36:58.468 15525 15545 F DEBUG   : Cause: null pointer dereference
04-19 00:36:58.468 15525 15545 F DEBUG   :     x0  0000000000000001  x1  000000680000c008  x2  0000006800014000  x3  000000025135412c
04-19 00:36:58.468 15525 15545 F DEBUG   :     x4  0000000001c9c380  x5  0000000000001f40  x6  0000000000000000  x7  7f7f7f7f7f7f7f7f
04-19 00:36:58.468 15525 15545 F DEBUG   :     x8  000000007fffffff  x9  8000000000000000  x10 0000000000000000  x11 00000002512f7800
04-19 00:36:58.468 15525 15545 F DEBUG   :     x12 00000000000026e0  x13 000000007fffffff  x14 000000000028361a  x15 0000012676ced7ce
04-19 00:36:58.468 15525 15545 F DEBUG   :     x16 0000000000000001  x17 0000000028b0aaab  x18 0000006eb4674000  x19 000000680000c000
04-19 00:36:58.468 15525 15545 F DEBUG   :     x20 0000000000000000  x21 0000006800008000  x22 0000006ec9401680  x23 000000025135412c
04-19 00:36:58.468 15525 15545 F DEBUG   :     x24 0000000000000000  x25 0000006ec94017b0  x26 0000006ec94017b4  x27 0000006ec94017b0
04-19 00:36:58.468 15525 15545 F DEBUG   :     x28 0000006ec94017c0  x29 0000006ec9401640
04-19 00:36:58.468 15525 15545 F DEBUG   :     lr  0000006e7c994b4c  sp  0000006ec9401270  pc  0000006e7c994b58  pst 0000000080001000
04-19 00:36:58.468 15525 15545 F DEBUG   : 22 total frames
04-19 00:36:58.468 15525 15545 F DEBUG   : backtrace:
04-19 00:36:58.469 15525 15545 F DEBUG   :       #00 pc 0000000005135b58  /data/app/~~lsmcqog_UWXHbBsrRXYsfA==/com.google.android.trichromelibrary_704910033-ZhAGhek8q6J91EnLqiDrVw==/base.apk!libmonochrome_64.so (offset 0x8dc000) (BuildId: a406330a9e112a5dc18c1374d04a51000725774e)
04-19 00:36:58.469 15525 15545 F DEBUG   :       #01 pc 0000000003f00d30  /data/app/~~lsmcqog_UWXHbBsrRXYsfA==/com.google.android.trichromelibrary_704910033-ZhAGhek8q6J91EnLqiDrVw==/base.apk!libmonochrome_64.so (offset 0x8dc000) (BuildId: a406330a9e112a5dc18c1374d04a51000725774e)

I’m struggling to debug where this issue lays, especially as it does not happen if I downgrade to 3.27.x. I’ve followed instructions from:

To try and get the symbols from the trace, but it fails with an Unknown engine hash message.

If anyone could point me in the right direction on how to go about working out what has caused the nullpointer dereference and crash, that would be fantastic!

Thank you.