> ## Documentation Index
> Fetch the complete documentation index at: https://namespace.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Out of memory (OOM) detection

export const CenteredImage = ({src, alt, width, caption, className}) => {
  const [basePath, setBasePath] = useState("");
  useEffect(() => {
    const path = window.location.pathname;
    setBasePath(path === "/docs" || path.startsWith("/docs/") ? "/docs" : "");
  }, []);
  return <Frame caption={caption} className={className} style={{
    maxWidth: width,
    marginInline: "auto"
  }}>
			<OptimizedImage src={`${basePath}${src}`} alt={alt} />
		</Frame>;
};

OOM detection is automatic. To find these warnings, open the [GitHub Actions dashboard](/docs/dashboard/github-actions), select a repository's workflow, open a run, and click a job to open its [job view](/docs/dashboard/github-actions#job-view).

Memory consumption graphs can already give insights on memory leaks and excessive allocation patterns.
However, when only working with memory allocation metrics it is hard to isolate if a job was running close to a memory limit, or encountered an error when running out of memory.
Namespace's automatic out of memory (OOM) detection makes these conditions explicit and simple to detect.

<CenteredImage width={600} alt="Job OOM Warning" src="/docs/images/github-actions/oom-job.webp" />

## Next steps

* [Debugging overview](/docs/solutions/github-actions/debugging)
* [Crash dumps](/docs/solutions/github-actions/debugging/crash-dumps)