How to Fix java.lang.OutOfMemoryError Crashes in Android Games

Even native-engine games carry a Java layer (ads, UI, plugins), and its heap is small — single-digit to low-hundreds of MB by device. Bitmaps and leaks fill it. Here is the cleanup.

How to fix it

1. Downsample every decoded image

Decode bitmaps at display size (inSampleSize/decode bounds first) — a full-camera-resolution image decoded for a thumbnail is the classic single-allocation OOM.

2. Hunt leaked contexts

Static fields, singletons, and long-lived listeners holding Activity references keep entire view trees alive — use LeakCanary in development; the leak trace names the holder.

3. Watch the ad SDK's appetite

Interstitial/rewarded ads decode large creatives on your heap — preload conservatively, release references after showing, and correlate OOM timing with ad events in your telemetry.

4. Segment crashes by RAM

OOM rate on 2–3 GB devices tells you your real floor — cap caches and features by ActivityManager's memory class instead of one-size-fits-all budgets.

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.