How to Fix iOS Jetsam Memory Terminations (EXC_RESOURCE) in Games

Jetsam kills are silent to players ('it just closed') and show as EXC_RESOURCE or jetsam events in diagnostics. The budget is the device's, not yours. Here is living within it.

How to fix it

1. Know the real ceilings

Footprint limits vary hugely by device generation — profile on your oldest supported iPhone with Instruments; the number there is your true budget, not what your Pro dev phone allows.

2. Flatten transition peaks

Loading the next area while the old one is resident doubles footprint exactly when you can least afford it — unload first, stream through a lightweight loading scene.

3. Honor memory warnings

Implement the memory-warning callbacks to drop caches, pools, and non-essential textures — apps that shed on warning survive pressure that kills apps that ignore it.

4. Watch the fleet metric

MetricKit/crash tooling exposes memory-termination rates per device model — a rising trend on 3–4 GB devices is your early alarm before reviews say 'crashes constantly'.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every mobile error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.