Skip to content

[Sentry: APP-63S] HybridApp iOS C++ bad_alloc OOM crash (follow-up to #93846) #101414

Open

Description

@arekm213

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:

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

Issue OwnerCurrent Issue Owner: @collectioneur

Activity

  1. mountiny commented on Nov 6, 2026

    @mountiny
    Contributor

    (Vit's agent) A second Sentry issue with the same signature is active on the latest production build: APP-MAB.

    • Users (last 14d): 4
    • Users (total since first seen): 7 (33 events)
    • First seen: 2026-09-23
    • Last seen: 2026-11-05, on 9.5.31-4 (App Store build)
    • Platform: iOS HybridApp. The latest event came from an iPad on iOS 26.6 with lowMemoryThreat: true
    • Mechanism: cpp_exception, C++ Exception: St9bad_alloc: std::bad_alloc, level fatal

    Like 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions