https://errorvault.dev/tags/heap-memory/ Recent content in Heap-Memory on ErrorVault — Developer Error Code Dictionary Hugo en-us Thu, 06 Aug 2026 00:44:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-memory-timeout-memory-timeout/ Thu, 06 Aug 2026 00:44:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-memory-timeout-memory-timeout/ <h2 id="1-symptoms">1. Symptoms</h2> <p>The <code>clw-memory-timeout</code> error manifests when the OpenClaw runtime detects that a memory-intensive operation has exceeded its allocated execution window. This error typically appears during container initialization, workload scheduling, or resource-intensive data processing pipelines where memory allocation requests cannot be fulfilled within the expected timeframe.</p> <p>When this error occurs, operators will observe the following indicators in their OpenClaw deployment logs:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>[ERROR] clw-memory-timeout: Memory allocation request exceeded timeout threshold </span></span><span style="display:flex;"><span>[TIMESTAMP] Worker node: worker-node-03 | Memory usage: 94.2% | Available swap: 0% </span></span><span style="display:flex;"><span>[WARN] GC pause duration: 2847ms (threshold: 2000ms) </span></span><span style="display:flex;"><span>[ERROR] Operation: heap-compaction | Duration: 45000ms | Limit: 30000ms </span></span><span style="display:flex;"><span>[FATAL] Unable to complete memory reclamation before deadline </span></span></code></pre></div><p>In the OpenClaw CLI, the error presents itself with an exit code of <strong>137</strong> and a descriptive message:</p> https://errorvault.dev/openclaw/openclaw-clw-api-oom-api-out-of-memory-error/ Fri, 31 Jul 2026 15:08:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-api-oom-api-out-of-memory-error/ <h2 id="1-symptoms">1. Symptoms</h2> <p>The <code>clw-api-oom</code> error manifests when the OpenClaw API service exhausts available memory resources during operation. This memory exhaustion produces several distinct observable symptoms that help identify the root cause and distinguish it from other runtime failures.</p> <p><strong>Primary Indicators:</strong></p> <ul> <li>API requests begin returning HTTP 503 Service Unavailable responses with extended latency</li> <li>Process termination events in system logs showing <code>exit code 137</code> (128 + SIGKILL signal)</li> <li>Progressive degradation in API response times as memory pressure increases</li> <li>Container or process restart cycles triggered by the orchestrator&rsquo;s health checks</li> <li>Memory usage metrics showing consumption approaching or exceeding configured limits</li> </ul> <p><strong>Shell Output Examples:</strong></p>