Repository navigation
Description
Sentry
https://expensify.sentry.io/issues/APP-63S
Impact (snapshot at filing)
- Users (total since first seen): 37
- Events: 369 (5 not covered by an existing fix, see Context)
- Users (last 14d): 0
- First seen: 2026-02-07
- Last seen: 2026-08-11 (for the events tracked here)
- Platform: iOS HybridApp, App Store builds
- App version(s): 9.4.43-1, 9.4.46-10, 9.4.49-3, 9.4.50-3
- Affected route(s): unknown (native OOM); breadcrumbs point at app start / foreground and the splash screen
- Mechanism:
cpp_exception - Level:
fatal
Stack trace (top frames, first-party only)
C++ Exception: St9bad_alloc (std::bad_alloc / OOM)
No crashed thread is reported. The exception is caught by SentryCrash's terminate handler without marking the throwing thread, so the frames shown in Sentry are nearest-symbol guesses, not the allocation that failed.
Context
State on 17 September 2026
This is a follow-up to #93846. St9bad_alloc just means "the app ran out of memory", so Sentry groups a lot of different OOM crashes under this one issue. Everything that was in it before is already resolved and not relevant here: the retryParams OOM (#95813), the receipt scanning OOM (#98769) and the GPS/Mapbox reconnect leak (#98891, confirmed by reproducing it on the old code, see the last comments in #93846).
What's left is these 5 events:
- 4 crashes from a single user on a 3 GB iPad (iPad12,2), all on app start or right after foregrounding. Same pattern every time: OldDot downloads ~11 MB at launch, ND downloads another ~11 MB right after
module.init,LOW_MEMORYshows up a few seconds later and the app dies.- Jul 28, 9.4.43-1: https://expensify.sentry.io/issues/APP-63S/events/94b4eb14d3074ee1b53c9f334a5fb1ac/
- Aug 1, 9.4.46-10: https://expensify.sentry.io/issues/APP-63S/events/bcf65b250a3542d2bc19cbd6a249c9a7/
- Aug 10, 9.4.50-3: https://expensify.sentry.io/issues/APP-63S/events/220cee95dd1b4afa894fc344b9c64304/
- Aug 10, 9.4.50-3 (2 seconds after coming back to the foreground): https://expensify.sentry.io/issues/APP-63S/events/9792abd1ab3c4533b6c33499b4bb28bf/
- 1 crash from an anonymous session (iPhone17,4) that sat on the splash screen for 16 hours and crashed on resume after duplicated downloads.
Nothing since Aug 11, that's over a month of silence, so to make any progress on these we need fresh events to work with.
Reproduction
Not reproduced. For now this is monitoring.
Related
- Prior GH issues: [Due for payment 2026-09-17] [$250] [Sentry: APP-63S] HybridApp iOS C++ bad_alloc OOM crash #93846 (original issue for APP-63S)
- Fixes for the OOMs previously grouped under APP-63S: Resolve OOM crash for high-traffic accounts caused by retryParams #95813, Fix OOM in ReceiptPreviews and ReceiptCell #98769, Fix layers ordering in GPSMapView #98891
Issue Owner
Current Issue Owner: @collectioneurMetadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsSUBISSUE
Activity
mountiny commentedon Nov 6, 2026
(Vit's agent) A second Sentry issue with the same signature is active on the latest production build: APP-MAB.
lowMemoryThreat: truecpp_exception,C++ Exception: St9bad_alloc: std::bad_alloc, levelfatalLike APP-63S, the event reports no crashed thread, so Sentry does not show the allocation that failed. I am linking it here instead of filing a separate issue because the signature and platform match.