openclaw - 💡(How to fix) Fix [Bug]: openclaw tui crashes with Maximum call stack size exceeded during schema compilation [2 comments, 2 participants]

Error trace from openclaw tui:

Failed to read config at C:\Users\liuqy.openclaw\openclaw.json RangeError: Maximum call stack size exceeded at writeOrBuffer (node:internal/streams/writable:567:21) at _write (node:internal/streams/writable:499:10) at Writable.write (node:internal/streams/writable:508:10) at console.error (node:internal/console/constructor:444:26) at writeConsoleLine Error compiling schema, function code: [enormous generated validator function] 17:49:28+08:00 [plugins] minimax failed to load: RangeError: Maximum call stack size exceeded 17:49:33+08:00 [plugins] google failed to load: RangeError: Maximum call stack size exceeded

Full log attached: 新建 文本文档 (2).txt (on desktop)

Note: openclaw plugins list --verbose runs successfully with no errors.

TL;DR

The issue can likely be fixed by updating or modifying the JSON schema to reduce its complexity and prevent the V8 stack overflow during compilation.

Guidance

• Investigate the openclaw.json config file and plugins for deeply nested or complex schema structures that may be causing the issue.
• Run openclaw plugins list --verbose to identify which plugins are loaded successfully and which ones are failing, and focus on the failing plugins' schema definitions.
• Consider simplifying or refactoring the schema to reduce its complexity and prevent the V8 stack overflow.
• As a temporary workaround, use the openclaw web command instead of openclaw tui to access the chat interface.

Example

No specific code example can be provided without more information about the schema structure, but reducing nested objects and arrays in the schema definition may help alleviate the issue.

Notes

The issue is specific to the openclaw tui command and does not affect openclaw web, suggesting that the problem lies in the TUI's schema compilation process. The openclaw plugins list --verbose command running successfully indicates that the issue is not with the plugins themselves, but rather with the schema compilation.

Recommendation

Apply a workaround by using openclaw web until the schema can be modified or updated to prevent the V8 stack overflow. This will allow users to access the chat interface while the issue is being resolved.