jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate

XLA could not allocate device memory. JAX preallocates ~75% of VRAM at first use by default, so an OOM here often reflects the preallocation policy or memory fragmentation across recompilations rather than a genuinely oversized model. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent jax failures.

Symptom

jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate

Root cause

XLA could not allocate device memory. JAX preallocates ~75% of VRAM at first use by default, so an OOM here often reflects the preallocation policy or memory fragmentation across recompilations rather than a genuinely oversized model. The decisive evidence is the first log line that precedes "jax.

Recommended fix

XLA_PYTHON_CLIENT_PREALLOCATE=false

How Denpex helps

Denpex investigates jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

The literal signature is "jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate". It is a distributed training failure associated with JAX, XLA, and multi-host accelerator meshes. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

XLA could not allocate device memory. JAX preallocates ~75% of VRAM at first use by default, so an OOM here often reflects the preallocation policy or memory fragmentation across recompilations rather than a genuinely oversized model. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

• The workload stops or loses forward progress after emitting "jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate".
• A retry on the same configuration reproduces the failure because the causal state has not changed.
• The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
• Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

• JAX, XLA, and multi-host accelerator meshes
• production-shaped multi-accelerator workloads
• containerized and bare-metal deployments of the same stack

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

• ✓Find the first occurrence of "jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓the message states the exact byte count requested, compare it against free VRAM. Check for repeated recompilation (jax.log_compiles(True)): each distinct input shape produces a new executable, and shape churn fragments the arena.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from latest checkpoint only after the control passes.

• XLA could not allocate device memory. JAX preallocates ~75% of VRAM at first use by default, so an OOM here often reflects the preallocation policy or memory fragmentation across recompilations rather than a genuinely oversized model.
• The decisive evidence is the first log line that precedes "jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.

jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate

Use this text as a lookup key in logs and upstream issue trackers. It is not presented as a captured customer log. Confirm the cause from your own preceding events, versions, configuration and the cited references.

try XLA_PYTHON_CLIENT_PREALLOCATE=false, or set XLA_PYTHON_CLIENT_MEM_FRACTION to a value that leaves room for other processes. If another process shares the GPU, preallocation is almost certainly the cause. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from latest checkpoint.

# Preserve evidence before restarting
rg -n -i 'error|exception|timeout|failed' <log-file>
nvidia-smi
python -m torch.utils.collect_env

# Find the exact signature in the complete log
rg -n -F -- "jax.errors.XlaRuntimeError: RESOURCE_EXHAUSTED: Out of memory while trying to allocate" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.