App still crashes in Memories

[earthly-alien]

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

• Yes

The bug

This is the same as #27439 which was closed as fixed. App still crashes in Memories frequently.

The OS that Immich Server is running on

Unraid

Version of Immich Server

v2.7.5

Version of Immich Mobile App

v2.7.4 build.3045

Platform with the issue

• Server
• Web
• Mobile

Device make and model

Samsung S25 Ultra

Your docker-compose.yml content

Same as original issue

Your .env content

/

Reproduction steps

1. Open Memories
2. Crash immediately or after several swipes to home screen

Relevant log output

05-29 20:00:10.161 20281 20318 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb4000071073111a0 in tid 20318 (ThreadPoolForeg), pid 20281 (alextran.immich)
05-29 20:00:10.699 20871 20871 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-29 20:00:10.699 20871 20871 F DEBUG   : Build fingerprint: 'samsung/pa3qxeea/pa3q:16/BP4A.251205.006/S938BXXS9CZE1_OXM9CZE1:user/release-keys'
05-29 20:00:10.699 20871 20871 F DEBUG   : Kernel Release: '6.6.98-android15-8-pe17667d-abogkiS938BXXS9CZE1-4k'
05-29 20:00:10.699 20871 20871 F DEBUG   : Revision: '11'
05-29 20:00:10.699 20871 20871 F DEBUG   : ABI: 'arm64'
05-29 20:00:10.699 20871 20871 F DEBUG   : Processor: '4'
05-29 20:00:10.699 20871 20871 F DEBUG   : Timestamp: 2026-05-29 20:00:10.291287311+0200
05-29 20:00:10.699 20871 20871 F DEBUG   : Process uptime: 111s
05-29 20:00:10.699 20871 20871 F DEBUG   : Executable: /system/bin/app_process64
05-29 20:00:10.699 20871 20871 F DEBUG   : Cmdline: app.alextran.immich
05-29 20:00:10.699 20871 20871 F DEBUG   : pid: 20281, tid: 20318, name: ThreadPoolForeg  >>> app.alextran.immich <<<
05-29 20:00:10.699 20871 20871 F DEBUG   : uid: 10526
05-29 20:00:10.699 20871 20871 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
05-29 20:00:10.699 20871 20871 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
05-29 20:00:10.699 20871 20871 F DEBUG   : esr: 0000000092000007 (Data Abort Exception 0x24)
05-29 20:00:10.699 20871 20871 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb4000071073111a0 (read)
05-29 20:00:10.699 20871 20871 F DEBUG   :     x0  b4000071073111a0  x1  0000000000114e60  x2  00000000ffffffff  x3  0000000000114f09
05-29 20:00:10.699 20871 20871 F DEBUG   :     x4  ffffffffffffffff  x5  00000000001912be  x6  00000000ffffffff  x7  6166383665313432
05-29 20:00:10.699 20871 20871 F DEBUG   :     x8  0000000000000000  x9  0000000000000001  x10 00000000000273f9  x11 000000007fffffff
05-29 20:00:10.699 20871 20871 F DEBUG   :     x12 00000075d423a0e0  x13 0000000034155555  x14 0000000000000018  x15 0000006bfb1dbacd
05-29 20:00:10.699 20871 20871 F DEBUG   :     x16 00ffffffffffffff  x17 000930b14de58089  x18 00000071b2c64000  x19 b4000071073111a0
05-29 20:00:10.699 20871 20871 F DEBUG   :     x20 0000000000114e60  x21 0000000000114e60  x22 b4000074cc552bd0  x23 b40000741c521da8
05-29 20:00:10.699 20871 20871 F DEBUG   :     x24 b4000074cc5c2cd0  x25 0000000000114e60  x26 0000000000000000  x27 0000000000000000
05-29 20:00:10.699 20871 20871 F DEBUG   :     x28 0000000000000001  x29 00000071b4a4a890
05-29 20:00:10.699 20871 20871 F DEBUG   :     lr  00000071b507add8  sp  00000071b4a4a890  pc  00000071b4cae594  pst 0000000020001000
05-29 20:00:10.699 20871 20871 F DEBUG   :     esr 0000000092000007
05-29 20:00:10.699 20871 20871 F DEBUG   : 18 total frames
05-29 20:00:10.699 20871 20871 F DEBUG   : backtrace:
05-29 20:00:10.699 20871 20871 F DEBUG   :       #00 pc 0000000000157594  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #01 pc 0000000000523dd4  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #02 pc 00000000002ebfa8  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #03 pc 00000000002e73dc  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #04 pc 0000000000293a40  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #05 pc 000000000022edac  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #06 pc 000000000022ee78  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #07 pc 0000000000212530  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #08 pc 0000000000236bb8  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #09 pc 0000000000236b1c  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #10 pc 00000000002365cc  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #11 pc 00000000002361b8  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #12 pc 000000000023dd10  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #13 pc 000000000023d9a0  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #14 pc 000000000023d870  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #15 pc 000000000024f368  /data/app/~~rQLnKanVMRs3Xi7K-pa5RQ==/com.google.android.gms-tEL1dfyinqUGMWLBSLqxeA==/split_CronetDynamite_installtime.apk!libcronet.148.0.7778.120.so (offset 0x94000) (BuildId: 0cb067fcee188859a443ab8b9f8ebe9f3f29c3a0)
05-29 20:00:10.699 20871 20871 F DEBUG   :       #16 pc 00000000000866ec  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+184) (BuildId: 0669c520dd58ab0634801cae537d6b06)
05-29 20:00:10.700 20871 20871 F DEBUG   :       #17 pc 000000000007900c  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: 0669c520dd58ab0634801cae537d6b06)

Additional information

No response

[alextran1502]

Do you know if you have really high-resolution photos on your device? like 100MP?

[earthly-alien]

It's possible there are a few 200MP photos, but I haven't experienced this issue on S23. For Memories it doesn't matter what resolution the photos are. It's very inconsistent. I can have the crash immediately after opening the first photo in Memories, but on the next try it can crash on the second photo, or any other really.

Edit: yes, there are several 200MP photos on the device.

[alextran1502]

I doubt that the stack trace is useful here, but maybe @santoshakil can perform some magic?

[santoshakil]

I doubt that the stack trace is useful here, but maybe @santoshakil can perform some magic?

on it...

[santoshakil]

@earthly-alien maybe this is related to the cronet buffer overflow on compressed responses that i fixed in #28439 + #28450. it's in main but hasn't gone out in a release yet, so 2.7.4 still has it.

would you be up for testing a build with the fix? if the crash stops, that confirms it. i can get you an apk.

(if you're behind a proxy or WAF that gzips responses, that's what sets it off — but the test build's the fastest way to know.)

[earthly-alien]

@santoshakil of course, happy to test.

I'm not behind a WAF. I do run nginx, but gzip isn't on.

[danieldietzler]

Before we go completely astray here, @earthly-alien when you opened this issue in the first place and you were saying it's still not fixed, you were using the release version 2.7.4, right? The PR that's fixing #27439 hasn't made it into any release yet.

[earthly-alien]

Has it been merged into 2.7.5? Because I'm still experiencing the same issue.

Edit: sorry, misread the last part. Do you know when it will be merged? Just so I can keep an eye if it continues to happen with the fix.

[danieldietzler]

We generally don't provide ETAs, but we're currently working on finalizing v3. Up until then I would close this PR then though, as this is just a duplicate of your original issue then and there's no indication of this still being an issue.