Quick answer: An out-of-memory (OOM) error occurs when the game requests memory the system cannot provide, because available RAM or VRAM is exhausted. The allocation fails and the game typically crashes. Causes include memory leaks, loading too many assets at once, or simply exceeding the memory budget of the platform, common on mobile and console.
An out-of-memory crash is the game hitting a hard wall: it needs memory, there is none left, and it dies. Unlike a logic bug, the immediate cause, an allocation that failed, is often innocent; the real culprit is whatever consumed all the memory beforehand. OOM errors are especially common on memory-constrained platforms like mobile and console, and understanding them is key to shipping a game that survives long sessions and limited hardware.
What Causes Out-of-Memory Errors
An OOM error has one proximate cause, a memory allocation that could not be satisfied, but several root causes. The most common is a memory leak: memory that should have been freed accumulates until none is left. Another is loading too much at once, pulling in more assets, textures, or data than the platform's memory can hold, perhaps a level that loads everything up front, or uncompressed textures that are larger than budgeted. A third is simply running on hardware with less memory than you designed for.
Because the failure happens when memory is finally exhausted, the crash often occurs in ordinary code that merely had the bad luck of asking for memory at the wrong moment. The allocation that fails is rarely the one at fault; the memory was consumed by something earlier, which is why diagnosing OOM means looking at overall memory usage, not just the line that crashed.
Why Platform Limits Matter
Memory is not infinite, and the limit varies enormously by platform. A PC with plenty of RAM is forgiving; a mobile device or a console with a fixed memory budget is not. Mobile platforms in particular will terminate apps that use too much memory, and console certification enforces memory budgets. A game that runs fine on your development PC can hit OOM crashes constantly on a low-memory phone, which is exactly the kind of platform-specific failure that only field data reveals.
VRAM (graphics memory) is a separate constraint that is easy to overlook. Loading too many or too-large textures can exhaust VRAM specifically, causing crashes on GPUs with less video memory even when system RAM is fine. Memory budgeting has to account for both.
Diagnosing OOM From Field Reports
OOM crashes are best diagnosed with field data that captures memory context. A crash report that records available memory, the device, and the platform at the moment of the OOM tells you whether you are leaking (memory grows over a session), over-loading (memory spikes at a specific point like a level load), or just exceeding a device's limit (crashes concentrated on low-memory hardware). Each diagnosis points at a different fix.
Bugnet captures device context including memory information and groups crashes by signature, so OOM crashes cluster together and arrive with the data to distinguish these cases. If OOM crashes concentrate on low-memory devices, you have a budgeting problem; if they correlate with long sessions, you have a leak; if they spike at a particular moment, you are loading too much there. That field evidence turns a generic 'out of memory' into a specific, fixable cause.
An out-of-memory crash is the game hitting a wall with no RAM left. The failing line is innocent, the real culprit is whatever ate the memory first.