Error map

memory limit Cloud Functions: Memory limit of X MiB exceeded — function killed

Google Cloud / Firebase · layer 6, Platform & cloud

Open the full error page →

Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

memory limit — Cloud Functions: Memory limit of X MiB exceeded — function killed (Google Cloud / Firebase)memory limitSIGSEGV — Segmentation fault (core dumped) (Linux)SIGSEGVMaxListenersExceededWarning — MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 listeners added (Node.js)MaxListenersExceede…Cannot allocate memory — fork: Cannot allocate memory / ENOMEM (Linux)Cannot allocate mem…OOM killer — Killed / Out of memory: Killed process (Linux OOM killer) (Linux)OOM killerEMFILE — Too many open files (EMFILE) (Linux)EMFILERequestEntityTooLargeException — Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException) (AWS)RequestEntityTooLar…Container memory limit exceeded — Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit (Google Cloud / Firebase)Container memory li…OOMKilled — Kubernetes: OOMKilled (exit code 137) (Kubernetes)OOMKilledheap out of memory — FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (Node.js)heap out of memoryMemoryError — MemoryError (Unable to allocate X GiB for an array) (Python)MemoryErrorJupyter kernel died — The kernel appears to have died. It will restart automatically. (Python)Jupyter kernel diedCloud Functions: Build failed — Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step) (Google Cloud / Firebase)Cloud Functions: Bu…CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffRangeError — RangeError: Maximum call stack size exceeded (JavaScript)RangeErrorinvalid string length — RangeError: Invalid string length (JavaScript)invalid string leng…OutOfMemoryError — java.lang.OutOfMemoryError: Java heap space (Java)OutOfMemoryErrorMEMORY_MANAGEMENT — Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A) (Windows)MEMORY_MANAGEMENTUnhandled 'error' event — Error: Unhandled 'error' event (events.js / node:events) (Node.js)Unhandled 'error' e…EADDRINUSE — Error: listen EADDRINUSE: address already in use :::3000 (Node.js)EADDRINUSEEPIPE — Error: write EPIPE (Node.js)EPIPEmaxBuffer exceeded — RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded (Node.js)maxBuffer exceededAllowed memory size exhausted — PHP Fatal error: Allowed memory size of X bytes exhausted (PHP)Allowed memory size…Composer memory — Composer: PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (PHP)Composer memoryrecovery mode — FATAL: the database system is in recovery mode (PostgreSQL)recovery modeENOENT — Error: ENOENT: no such file or directory (Node.js)ENOENTECONNRESET — Error: socket hang up / read ECONNRESET (API)ECONNRESET1040 — MySQL ERROR 1040 (08004): Too many connections (MySQL)1040413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413Task timed out — AWS Lambda: Task timed out after X seconds (AWS)Task timed outRuntime.ImportModuleError — Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'x' (AWS)Runtime.ImportModul…Gradle Java heap space — Gradle: Expiring Daemon because JVM heap space is exhausted / java.lang.OutOfMemoryError: Java heap space during build (Android)Gradle Java heap sp…Process completed with exit code 137 — GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory) (CI/CD)Process completed w…Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container exceeded …ELIFECYCLE — npm ERR! code ELIFECYCLE / Command failed with exit code 1 (npm)ELIFECYCLEEvicted — Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage (Kubernetes)EvictedRuntime exited with error: signal: killed — Lambda: Runtime exited with error: signal: killed (Runtime.ExitError) (AWS)Runtime exited with…0xC0000005 — The application was unable to start correctly (0xc0000005) / Exception code 0xc0000005 access violation (Windows)0xC0000005OutOfMemoryException — System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown (.NET)OutOfMemoryExceptionEXC_BAD_ACCESS — Thread 1: EXC_BAD_ACCESS (code=1, address=0x0) (iOS)EXC_BAD_ACCESSdouble free or corruption — C/C++: free(): double free detected / double free or corruption (out) — Aborted (core dumped) (C/C++)double free or corr…OOM command not allowed — Redis: OOM command not allowed when used memory > 'maxmemory' (Redis)OOM command not all…mongod killed by OOM killer — MongoDB: Out of memory: Killed process (mongod) — WiredTiger cache + queries exhausted RAM (MongoDB)mongod killed by OO…Sort/Group exceeded memory limit of 100 MB (allowDiskUse) — MongoServerError: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in (MongoDB)Sort/Group exceeded…Client output buffer limit reached (scheduled to be closed) — Redis: Client id=12 addr=10.0.0.5:51234 scheduled to be closed ASAP for overcoming of output buffer limits (Redis)Client output buffe…Keys disappear: maxmemory eviction (allkeys-lru) — Redis: evicted_keys growing — keys vanish unexpectedly because maxmemory is reached and a volatile/allkeys eviction policy is active (Redis)Keys disappear: max…COPY failed — COPY failed: file not found in build context / "/app/x": not found (Docker)COPY failedERR_OSSL_EVP_UNSUPPORTED — Error: error:0308010C:digital envelope routines::unsupported (Node.js)ERR_OSSL_EVP_UNSUPP…prisma generate — Error: @prisma/client did not initialize yet. Please run "prisma generate" (Node.js)prisma generate

Directly related (12)

SIGSEGVLinux

Segmentation fault (core dumped)

A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).

MaxListenersExceededWarningNode.js

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 listeners added

More than 10 listeners were added to one event — often a leak where listeners are added repeatedly.

Cannot allocate memoryLinux

fork: Cannot allocate memory / ENOMEM

The kernel refused a memory allocation — RAM and swap are exhausted, or overcommit/cgroup limits block it.

OOM killerLinux

Killed / Out of memory: Killed process (Linux OOM killer)

The kernel ran out of memory and killed a process to recover — the program just prints “Killed” (exit code 137).

EMFILELinux

Too many open files (EMFILE)

The process hit its file-descriptor limit — sockets, files and pipes all count.

RequestEntityTooLargeExceptionAWS

Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)

The event payload (or response) is over Lambda’s 6 MB synchronous limit (256 KB for async invocations).

Container memory limit exceededGoogle Cloud / Firebase

Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit

The container used more memory than the Cloud Run service allows, so the instance was terminated.

OOMKilledKubernetes

Kubernetes: OOMKilled (exit code 137)

The container used more memory than its limit, and the kernel killed it.

heap out of memoryNode.js

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

The V8 heap hit its limit — a large build (webpack, tsc, Next.js) needs more memory, or the app leaks.

MemoryErrorPython

MemoryError (Unable to allocate X GiB for an array)

Python couldn’t allocate memory — the data is larger than available RAM or address space.

Jupyter kernel diedPython

The kernel appears to have died. It will restart automatically.

The Jupyter kernel process crashed — usually out of memory or a native library crash.

Cloud Functions: Build failedGoogle Cloud / Firebase

Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)

The deployment's build step (Cloud Build) failed, so no new function version was created.

Two steps away (36)

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

RangeErrorJavaScript

RangeError: Maximum call stack size exceeded

A function called itself (directly or indirectly) too many times — usually infinite recursion.

invalid string lengthJavaScript

RangeError: Invalid string length

A string grew beyond the engine’s maximum length — usually runaway concatenation or huge JSON.stringify output.

OutOfMemoryErrorJava

java.lang.OutOfMemoryError: Java heap space

The JVM ran out of heap memory and garbage collection couldn’t free enough.

MEMORY_MANAGEMENTWindows

Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)

Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.

Unhandled 'error' eventNode.js

Error: Unhandled 'error' event (events.js / node:events)

An EventEmitter (stream, socket, child process, server) emitted 'error' and nothing listened for it, so Node crashed.

EADDRINUSENode.js

Error: listen EADDRINUSE: address already in use :::3000

Another process is already listening on that port.

EPIPENode.js

Error: write EPIPE

Node wrote to a pipe or socket whose other end was already closed.

maxBuffer exceededNode.js

RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded

child_process.exec/execSync produced more output than its buffer allows (default 1 MB).

Allowed memory size exhaustedPHP

PHP Fatal error: Allowed memory size of X bytes exhausted

The script tried to use more memory than PHP’s `memory_limit` allows.

Composer memoryPHP

Composer: PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted

Composer ran out of memory while resolving or installing dependencies.

recovery modePostgreSQL

FATAL: the database system is in recovery mode

PostgreSQL crashed (often OOM-killed) and is replaying WAL to recover.

ENOENTNode.js

Error: ENOENT: no such file or directory

A file or directory the program tried to open doesn’t exist at that path.

ECONNRESETAPI

Error: socket hang up / read ECONNRESET

The other side closed the TCP connection abruptly while your client was still using it.

1040MySQL

MySQL ERROR 1040 (08004): Too many connections

MySQL reached `max_connections` and refuses new clients.

413HTTP

HTTP 413 Content Too Large (Request Entity Too Large)

The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.

Task timed outAWS

AWS Lambda: Task timed out after X seconds

The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.

Runtime.ImportModuleErrorAWS

Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'x'

Lambda couldn’t load your handler file or one of its dependencies — the package is missing from the deployment zip/layer or the h…

Gradle Java heap spaceAndroid

Gradle: Expiring Daemon because JVM heap space is exhausted / java.lang.OutOfMemoryError: Java heap space during build

The Gradle daemon (or Kotlin daemon) ran out of memory compiling or dexing the project.

Process completed with exit code 137CI/CD

GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory)

The command was killed by the system with SIGKILL (128 + 9), almost always because the runner ran out of memory.

Container exceeded memory limitCI/CD

Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137

A Bitbucket Pipelines step used more memory than the step allows (4 GB by default, 1 GB for service containers) and was killed.

ELIFECYCLEnpm

npm ERR! code ELIFECYCLE / Command failed with exit code 1

An npm script (build, start, test, postinstall) exited with an error. ELIFECYCLE is only the wrapper — the real error is printed…

EvictedKubernetes

Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage

The kubelet removed the pod because its node ran short of memory or disk.

Runtime exited with error: signal: killedAWS

Lambda: Runtime exited with error: signal: killed (Runtime.ExitError)

The function process was killed — almost always because it ran out of its configured memory.

0xC0000005Windows

The application was unable to start correctly (0xc0000005) / Exception code 0xc0000005 access violation

A program tried to read or write memory it doesn’t own and Windows stopped it — buggy software, bad drivers/plugins, security sof…

OutOfMemoryException.NET

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown

The process couldn’t allocate memory — large in-memory data, leaks, 32-bit process limits, or container memory limits.

EXC_BAD_ACCESSiOS

Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

The app accessed memory it shouldn’t — a dangling pointer, released object, unsafe pointer misuse, a data race, or infinite recur…

double free or corruptionC/C++

C/C++: free(): double free detected / double free or corruption (out) — Aborted (core dumped)

Memory was freed twice or the heap was corrupted (buffer overflow, freeing a non-heap pointer), so glibc aborted the program.

OOM command not allowedRedis

Redis: OOM command not allowed when used memory > 'maxmemory'

Redis reached its maxmemory limit and the eviction policy (noeviction) refuses new writes.

mongod killed by OOM killerMongoDB

MongoDB: Out of memory: Killed process (mongod) — WiredTiger cache + queries exhausted RAM

The Linux OOM killer terminated `mongod` because the host ran out of memory.

Sort/Group exceeded memory limit of 100 MB (allowDiskUse)MongoDB

MongoServerError: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in

An aggregation stage needed more than 100 MB of RAM and spilling to disk wasn't enabled.

Client output buffer limit reached (scheduled to be closed)Redis

Redis: Client id=12 addr=10.0.0.5:51234 scheduled to be closed ASAP for overcoming of output buffer limits

A client (often a slow subscriber or a replica) couldn't read data fast enough, so Redis disconnected it to protect memory.

Keys disappear: maxmemory eviction (allkeys-lru)Redis

Redis: evicted_keys growing — keys vanish unexpectedly because maxmemory is reached and a volatile/allkeys eviction policy is active

Redis removed keys to stay under `maxmemory` according to the eviction policy.

COPY failedDocker

COPY failed: file not found in build context / "/app/x": not found

The Dockerfile COPY refers to a path outside the build context, excluded by .dockerignore, or relative to the wrong directory.

ERR_OSSL_EVP_UNSUPPORTEDNode.js

Error: error:0308010C:digital envelope routines::unsupported

An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.

prisma generateNode.js

Error: @prisma/client did not initialize yet. Please run "prisma generate"

The generated Prisma Client is missing or out of date.