Why a PHP Script "Eats" 128 MB and How to Deal with It

"Allowed Memory Size of 134217728 Bytes Exhausted" — The Emergency Brake of Your PHP Application

Have you ever seen this message in the middle of the night, when your site suddenly crashes, and the logs show white text on a black background? If so, you are not alone. Thousands of developers on Stack Overflow have wondered why their seemingly harmless PHP script suddenly "eats" all 128 megabytes of RAM and crashes with a fatal error.

Let's figure out what this error actually means, why it occurs, and most importantly, how to fix it once and for all. We won't just increase the memory limit — we'll learn to write code that doesn't gobble up resources like a hungry student in a cafeteria.

What Does "134217728 Bytes Exhausted" Mean?

The number 134,217,728 is 128 megabytes. That's how much memory PHP is allowed to use for your script by default. When the script tries to allocate more — boom! — and you get a Fatal Error. This is a protective mechanism that prevents one script from killing the entire server.

But here's the catch: 128 MB is very little for modern applications. Processing a large XML file, generating a report from a database, working with images or heavy libraries — all of this can easily exceed the limit.

Why Does This Happen? Three Main Reasons

\n
• Greedy loops and recursion — when you load all data into memory at once, instead of processing it in chunks.
\n
• Memory leaks — static variables, global arrays, and improper use of static can accumulate data.
\n
• Heavy libraries and extensions — for example, image processing via GD or working with PDF.
\n

How to Fix the Error: From Simple to Complex

Method 1: Increase the Memory Limit (Quick Fix)

The most obvious path is to simply give PHP more memory. But remember: this is not a cure, it's a painkiller. If your code is poorly written, it will eat up 512 MB and 1 GB as well.

There are three ways to increase the limit:

1. In the php.ini file (permanent change):

memory_limit = 256M

2. In .htaccess (if available):

php_value memory_limit 256M

3. In the script itself (only for the current execution):

ini_set('memory_limit', '256M');

But be warned: if you are on shared hosting, the host may not allow you to increase the limit above a certain threshold. And even if it does — don't abuse it.

Method 2: Code Optimization — The Real Solution

Instead of giving the script more memory, let's teach it to use what it has wisely.

Use unset() to Free Memory

PHP is not C++, but manual memory management still works. When a large variable is no longer needed — delete it:

$data = file_get_contents('huge_file.csv');\n// process the data\nprocessData($data);\n// free the memory\nunset($data);\n

Process Data in Chunks

Instead of loading 100,000 rows from the database into memory, use cursors or limits:

// BAD: load everything into memory\n$users = $db->query("SELECT * FROM users")->fetchAll();\n\n// GOOD: process one row at a time\n$stmt = $db->query("SELECT * FROM users");\nwhile ($row = $stmt->fetch()) {\n    processUser($row);\n    // PHP will free memory after each iteration\n}\n

Use Generators (yield)

Generators are magic for working with large datasets. They don't store all values in memory:

function getLargeData() {\n    for ($i = 0; $i < 1000000; $i++) {\n        yield $i;\n    }\n}\n\nforeach (getLargeData() as $value) {\n    // process one element at a time\n    echo $value . "\\n";\n}\