Error map
Container memory limit exceeded Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit
Google Cloud / Firebase · layer 6, Platform & cloud
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.
Directly related (12)
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.
MemoryError (Unable to allocate X GiB for an array)
Python couldn’t allocate memory — the data is larger than available RAM or address space.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
The kernel appears to have died. It will restart automatically.
The Jupyter kernel process crashed — usually out of memory or a native library crash.
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.
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.
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.
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.
Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout
The request ran longer than the service's request timeout (default 5 minutes, max 60), so Cloud Run closed it.
Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance
Cloud Run could not serve the request: no instance was ready, instances crashed, or the service hit its max-instances/concurrency…
Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server
The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.
Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied
Cloud Run cannot pull the container image — it doesn't exist, the tag is wrong, or the service identity lacks access to the regis…
Two steps away (35)
java.lang.OutOfMemoryError: Java heap space
The JVM ran out of heap memory and garbage collection couldn’t free enough.
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
Segmentation fault (core dumped)
A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).
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).
RangeError: Invalid string length
A string grew beyond the engine’s maximum length — usually runaway concatenation or huge JSON.stringify output.
Lambda: Runtime exited with error: signal: killed (Runtime.ExitError)
The function process was killed — almost always because it ran out of its configured memory.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
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…
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.
fork: Cannot allocate memory / ENOMEM
The kernel refused a memory allocation — RAM and swap are exhausted, or overcommit/cgroup limits block it.
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…
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.
GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?
A docker-in-docker job could not reach the `docker:dind` service — it is not started, not privileged, or the TLS/host settings do…
Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline
A Jenkins build is queued because no executor with the required label is free or the agent is offline.
CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded
A CircleCI step printed nothing for 10 minutes, so CircleCI assumed it hung and cancelled it.
Gradle: Could not resolve all files for configuration / Could not resolve dependency
Gradle couldn’t download a dependency — wrong coordinates/version, missing repository, offline mode, or network/proxy issues.
! [remote rejected] main -> main (shallow update not allowed)
You pushed from a shallow clone to a remote that doesn’t accept shallow history.
remote: Permission to owner/repo.git denied to github-actions[bot]. fatal: unable to access … The requested URL returned error: 403
A GitHub Actions workflow tried to push but the GITHUB_TOKEN doesn’t have write permission.
GitHub Actions: Error: Process completed with exit code 1.
A `run:` command returned a non-zero status, so the step (and job) failed — the real cause is printed in the log lines above.
GitHub Actions: Error: Process completed with exit code 127 — command not found
The shell could not find the command you tried to run: it is not installed on the runner, not on PATH, or misspelled.
GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled
The machine running your job was shut down or reclaimed while the job was running — a self-hosted runner stopped, a spot instance…
FATAL: the database system is in recovery mode
PostgreSQL crashed (often OOM-killed) and is replaying WAL to recover.
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…
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.
Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting
The Google API you called is not enabled for the project that the request is billed to.
gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file
Application Default Credentials bill API usage to a different project than the one you have set as active, which can cause surpri…
Cloud Functions: Function execution took 60002 ms, finished with status: 'timeout'
The function ran past its timeout (default 60s for HTTP 1st gen) and was terminated.
Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Cloud Run started your container, but nothing listened on $PORT within the startup timeout — the app crashed, listens on another…
GKE Ingress: Some backend services are in UNHEALTHY state / 502 Server Error from the load balancer
The Google load balancer's health checks fail for the Ingress backends, so it returns 502 or 'no healthy upstream'.
Cloud SQL: FATAL: remaining connection slots are reserved / MySQL: ERROR 1040 (08004): Too many connections
The instance's maximum connections was reached, often because serverless instances each open their own connection pool.
GKE: google.api_core.exceptions.Forbidden: 403 Caller does not have required permission — Workload Identity: unable to generate access token
A pod tried to call Google APIs but its Kubernetes service account is not bound to a Google service account (or the binding lacks…
Google Cloud: 403 PERMISSION_DENIED — Permission 'storage.objects.get' denied on resource (or it may not exist)
The caller's identity lacks the IAM permission named in the message on that resource.
GCP: FAILED_PRECONDITION: Key creation is not allowed on this service account (constraints/iam.disableServiceAccountKeyCreation)
An organisation policy forbids creating downloadable JSON keys for service accounts.
exec /usr/local/bin/docker-entrypoint.sh: exec format error
The container tried to run a binary built for a different CPU architecture (arm64 vs amd64) — or a script with a broken shebang /…
Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
Your identity cannot push or pull images in that Artifact Registry repository, or Docker isn't authenticated to the registry host.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError