What causes OpenClaw web_fetch memory leak?

Chrome renderer processes spawned by web_fetch are never terminated after use. They accumulate over time, eventually consuming all available RAM.

How much memory does the OpenClaw Chrome renderer leak use?

After 24 hours of normal use, 46 Chrome renderer processes consumed 2.6GB RAM on a 3.7GB VPS, reaching 91% RAM usage.

Will the OpenClaw web_fetch memory leak crash my server?

Yes, on constrained servers (4GB or less) this can cause OOM crashes within 24 hours of normal web_fetch usage.

How to fix OpenClaw Chrome renderer memory leak?

Manually kill orphaned Chrome processes periodically, or set up a cron job to clean up renderer processes. No official fix yet.

Is the OpenClaw web_fetch Chrome leak a known issue?

Yes, multiple GitHub issues document it (#70270, #29685, #11257). The problem has existed since early 2026 across versions.

← Back to dashboard

clawsmith.com/signal/openclaw-web-fetch-chrome-renderer-memory-leak

⚠ IssueWide OpencoreLive

OpenClaw web_fetch Chrome Renderer Processes Accumulate and Never Clean Up

When using web_fetch (headless Chrome browser tool), renderer processes accumulate over time and are never terminated. After 24 hours of normal use, Chrome renderer count grew to 46 processes consuming 2.6GB RAM on a 3.7GB VPS, causing OOM crashes.

Social Proof 2 sources

web_fetch: Chrome renderer processes accumulate and are never cleaned up

gh:HendrikHarren · 4/22/2026

0 GH

Browser renderer processes accumulate without cleanup, causing OOM

3/1/2026

Frequently Asked Questions

Virality Score

across 1 platforms

Details

Signalissue

Ecosystemcore

Sources2

Platforms1

Updated7h ago

Trend→ stable

Top ideas

All ideas →

26.1MA pre-publish scanner that strips source maps, secrets, and internal code from npm packages before they ship to the registry 2.2MA routing middleware that pairs an expensive advisor model with a cheap executor model for OpenClaw agents, cutting API costs by 80% while maintaining output quality 892.2KA web dashboard that finds revenue gaps and saturated niches across 180+ OpenClaw startups in real time

Related signals

All signals →

445Claude Code Memory Leak Crisis: 19 Incidents in 14 Days, 11.6GB Per Window