openclaw - 💡(How to fix) Fix [Bug] 2026.4.2 tasks maintenance still hits plugin stack overflow (RangeError) [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#61851Fetched 2026-04-08 02:53:33
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
1
Timeline (top)
commented ×1

Root Cause

The fix appears to be on main branch (commit 9a03fe8181 - facade recursion guard) but has not been released to stable channel yet. Issue #57023 was closed as fixed on 2026-03-31, but the stable releases (2026.4.2 and 2026.4.5) still contain the bug.

RAW_BUFFERClick to expand / collapse

Bug Description

OpenClaw 2026.4.2 (d74a122) still hits RangeError: Maximum call stack size exceeded when running tasks maintenance, similar to issues #57023 and #56980 which were closed as fixed on main branch.

Plugins Affected

  • amazon-bedrock
  • google
  • minimax
  • talk-voice

All report: \RangeError: Maximum call stack size exceeded\ during tasks maintenance.

Environment

  • Version: 2026.4.2 (also affects 2026.4.5)
  • Install: pnpm global
  • Platform: Windows 10.0.22631
  • Node: 24.14.0

Analysis

The fix appears to be on main branch (commit 9a03fe8181 - facade recursion guard) but has not been released to stable channel yet. Issue #57023 was closed as fixed on 2026-03-31, but the stable releases (2026.4.2 and 2026.4.5) still contain the bug.

Expected

tasks maintenance should complete without stack overflow. The fix that landed on main should be included in the next stable release.

extent analysis

TL;DR

The issue can be resolved by waiting for the next stable release that includes the fix for the RangeError or by using the main branch where the fix has already been applied.

Guidance

  • The bug is caused by a missing recursion guard, which has been fixed in the main branch (commit 9a03fe8181) but not yet released to the stable channel.
  • To verify if the fix is working, run tasks maintenance after updating to the main branch or the next stable release.
  • Consider using the main branch temporarily until the stable release is available, but be aware that the main branch may contain other unstable changes.
  • Monitor the release notes for the next stable version to ensure it includes the fix for the RangeError.

Example

No code snippet is provided as the issue does not require a code-level fix, but rather a version update or branch switch.

Notes

The solution relies on waiting for an official release or switching to the main branch, which may introduce other instability. It's essential to weigh the risks and benefits of using the main branch temporarily.

Recommendation

Apply workaround by using the main branch until the next stable release is available, as it includes the necessary fix for the RangeError, but be cautious of potential instability.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING