“Out of memory” means your computer has run out of the temporary workspace it uses to run programs. This workspace is your RAM (random access memory), the fast, short-term storage where your operating system and every open application live while they’re active. When there’s no more room, your system can’t launch new programs, open new browser tabs, or keep running what’s already open. The result is error messages, frozen screens, or crashed applications.
How Your Computer Uses Memory
RAM is different from your hard drive or SSD. Your drive stores files permanently: documents, photos, installed programs. RAM holds whatever your computer is actively working on right now. When you open a web browser, your system loads parts of that program into RAM so it can respond instantly. When you close the browser, that RAM gets freed up for something else.
The key limitation is that RAM is finite. A typical computer today has 8 to 16 GB of it. Windows 11 requires a minimum of 4 GB just for the operating system, and Microsoft’s newer Copilot+ PCs ship with 16 GB as a baseline. Every open application, browser tab, and background process claims a slice of that pool. When the total demand exceeds what’s available, you’re out of memory.
Your operating system does have a fallback. When RAM fills up, it starts using a portion of your hard drive as overflow storage, called swap space or a page file. This technically expands your available memory, but hard drives are dramatically slower than RAM. So instead of an instant crash, you first notice everything grinding to a crawl as your system shuffles data back and forth between RAM and disk. If even that overflow space fills up, you get the out of memory error.
What It Looks and Feels Like
An out of memory situation doesn’t always announce itself with a neat error message. Often it creeps in gradually. Your computer slows down for no obvious reason. Clicks take a few seconds to register. Applications freeze mid-task, and you see the spinning wheel or “not responding” label. In more severe cases, you might notice visual glitches: garbled text, flickering screens, or images rendering incorrectly. These can also indicate faulty RAM hardware, but temporary memory exhaustion produces similar symptoms.
The most recognizable version is an explicit error. Chrome, for instance, will display an “Aw, Snap! Not enough memory” page when a tab can’t get the resources it needs. Games might crash to the desktop. Creative software like Photoshop or video editors will refuse to apply a filter or export a file. On Linux systems, the operating system itself may step in with a process called the OOM Killer, which forcibly shuts down whichever program is consuming the most memory to keep the rest of the system alive.
Why It Happens
The simplest cause is just having too many things open at once. But several specific patterns make it worse.
- Browser tabs. Chrome is the most common offender here. Each tab runs as its own process, and even inactive tabs continue consuming RAM in the background. A dozen open tabs can easily eat several gigabytes. Extensions add to the problem, especially ad blockers, translation tools, or productivity add-ons that run on every page you visit.
- Memory leaks. Sometimes software claims memory and never gives it back. This happens when a program keeps references to data it no longer needs, preventing the system from reclaiming that space. The longer the program runs, the more memory it hoards. This is why restarting an application or rebooting your computer often fixes the problem temporarily.
- Large files and datasets. Opening a massive spreadsheet, editing high-resolution video, or running a game with heavy texture packs can exceed your available RAM in a single application.
- Background processes. Software you’ve forgotten about, including startup programs, cloud sync tools, antivirus scans, and system updaters, all claim memory even when you’re not interacting with them.
Fixing It in the Moment
When you hit an out of memory error, the fastest fix is freeing up RAM by closing things you don’t need. Start with browser tabs, since they’re usually the biggest offenders. Then close any applications running in the background. On Windows, open Task Manager (Ctrl + Shift + Esc) and sort by memory usage to see what’s consuming the most. On macOS, Activity Monitor shows the same information. End anything non-essential.
If you’re getting the error specifically in Chrome, the browser has a built-in feature called Memory Saver that automatically suspends inactive tabs. You can find it in Chrome’s settings under Performance, where you can choose between Standard, Balanced, and Maximum modes. Setting it to Maximum is the most aggressive about freeing up memory from tabs you’re not actively viewing. Also make sure Chrome is up to date, since older versions are more prone to memory leaks. Disabling hardware acceleration in Chrome’s settings can also help, since that feature offloads graphics processing in a way that sometimes consumes extra memory.
A simple restart of your computer clears RAM entirely and resolves any memory leaks that have built up over time. If you tend to leave your computer on for days or weeks, periodic restarts can prevent these errors from accumulating.
Preventing It Long Term
If out of memory errors happen regularly, your system probably doesn’t have enough RAM for how you use it. The 4 GB minimum that Windows 11 requires is genuinely bare-bones. For general browsing and office work, 8 GB is a more realistic floor. If you run creative software, play modern games, or regularly have dozens of browser tabs open, 16 GB is the practical sweet spot. Professional workloads like video editing or software development often benefit from 32 GB.
On desktop computers, adding more RAM is usually straightforward and relatively affordable. Laptops are trickier since many modern models have RAM soldered to the motherboard, making upgrades impossible. Check your specific model before assuming you can add more.
Windows manages its virtual memory (page file) automatically, and in most cases you should leave those settings alone. Manually adjusting the page file size can cause stability issues if done incorrectly. The one exception is specific software that explicitly recommends a larger page file, which some heavily modded games do. In that case, follow the software’s instructions rather than applying a general rule.
For Developers: Heap vs. Stack
If you’re a programmer encountering out of memory errors in your own code, the issue is almost always heap exhaustion. The heap is where your program stores data that needs to persist beyond a single function call: objects, arrays, data structures. It can grow to consume as much memory as the operating system will allow. When it runs out, memory allocation calls fail, and your program crashes or throws an exception.
Stack overflow is a related but different problem. The stack is a much smaller region of memory, typically 1 to 5 MB, used for function calls and local variables. It overflows when functions call themselves recursively without a proper stopping point, or when you try to allocate a very large variable inside a function. The error message is different (“stack overflow” rather than “out of memory”), and the fix is different too.
The most common causes of heap exhaustion in application code are unreleased object references, growing collections that never get cleared, unclosed file handles or database connections, and event listeners that remain attached after their associated elements are removed. In garbage-collected languages like Java, Python, or JavaScript, these patterns prevent the runtime from reclaiming memory it would otherwise free automatically. Profiling tools built into most development environments can pinpoint exactly where memory is being held.