openclaw - 💡(How to fix) Fix [Bug]: text RangeError: Maximum call stack size exceeded [1 comments, 2 participants]

RangeError: Maximum call stack size exceeded

Steps to reproduce

openclaw-control-ui-attachment-stack-overflow-report.md

Expected behavior

• PDF / 长图上传后应正常进入附件解析或媒体 offload 流程。
• 如果文件过大或格式不支持，应返回明确、可操作的错误，例如：

TL;DR

The issue is likely caused by an infinite recursion or a very deep call stack when handling large PDF or image files in the OpenClaw Control UI, and a workaround may involve increasing the maximum call stack size or optimizing the file processing logic.

Guidance

• Review the chat.send stage in the OpenClaw Control UI code to identify potential recursive function calls or deeply nested loops that could be causing the stack overflow.
• Consider adding error handling or input validation to prevent large files from being processed in a way that exceeds the maximum call stack size.
• Investigate the file processing logic to see if there are any optimizations that can be made to reduce the number of function calls or loop iterations.
• Check if there are any existing configuration options or settings that can be adjusted to increase the maximum call stack size or improve performance.

Example

No specific code example can be provided without more information about the OpenClaw Control UI codebase, but a general example of how to increase the maximum call stack size in Node.js might look like:

// Increase the maximum call stack size
const v8 = require('v8');
v8.setFlagsFromString('--max_call_stack_size=10000');

However, this is just a hypothetical example and may not be applicable to the specific issue at hand.

Notes

The root cause of the issue is unclear without more information about the OpenClaw Control UI code and the specific file processing logic. Further investigation and debugging are needed to determine the best course of action.

Recommendation

Apply a workaround, such as increasing the maximum call stack size or optimizing the file processing logic, as the root cause of the issue is unclear and a full fix may require more information or debugging.