Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix gateway: RangeError Maximum call stack size in chat.send attachment parse/stage (v2026.5.3-1) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#81349•Fetched 2026-05-14 03:33:03
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
1
Author
adapepperadapepper
Participants
adapepperadapepperclawsweeper[bot]clawsweeper[bot]
Timeline (top)
closed ×1commented ×1

Error Message

attachment parse with a friendly error message

Fix Action

Fix / Workaround

Customer impact: Todd Bolyard (go-yard) — workaround was to recreate his instance onto v2026.5.7 and force re-seed of .npm-prefix.

RAW_BUFFERClick to expand / collapse

Priority: 🟠 High

Repro:

  • OpenClaw 2026.5.3-1 (commit 2eae30e), embedded in sandpaw-base
  • Customer attaches a multi-page PDF + types a long chat message
  • Gateway logs: [gateway] chat.send attachment parse/stage failed: RangeError: Maximum call stack size exceeded [ws] ⇄ res ✗ chat.send 418ms errorCode=INVALID_REQUEST errorMessage=RangeError: Maximum call stack size exceeded

v2026.5.7 (eeef486) — UNVERIFIED whether the fix landed. Need to:

  1. Reproduce on v2026.5.3-1 in a controlled test
  2. Test same payload on v2026.5.7
  3. If fixed: identify the commit, cherry-pick-test note
  4. If NOT fixed: file an issue on openclaw/openclaw with a minimal repro PDF + attached config, link the gateway log, propose a stack-depth cap on attachment parse with a friendly error message

Customer impact: Todd Bolyard (go-yard) — workaround was to recreate his instance onto v2026.5.7 and force re-seed of .npm-prefix.

Migrated from ada-memory task openclaw-attachment-rangeerror-bug

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API middleware#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix gateway: RangeError Maximum call stack size in chat.send attachment parse/stage (v2026.5.3-1) [1 comments, 2 participants]