openclaw - 💡(How to fix) Fix [Bug]: Built-in plugins (minimax, google, talk-voice) fail with RangeError: Maximum call stack size exceeded on Windows [1 comments, 2 participants]

[plugins] minimax failed to load from .../openclaw/dist/extensions/minimax/index.js: RangeError: Maximum call stack size exceeded [plugins] google failed to load from .../openclaw/dist/extensions/google/index.js: RangeError: Maximum call stack size exceeded [plugins] talk-voice failed to load from .../openclaw/dist/extensions/talk-voice/index.js: RangeError: Maximum call stack size exceeded

TL;DR

Setting the NODE_OPTIONS environment variable to --stack-size=65536 resolves the issue by increasing the Node.js default call stack size.

Guidance

• Verify the issue is resolved by loading a problematic module with an increased stack size using node --stack-size=65536 -e require("./minimax/index.js").
• To apply the fix, set the NODE_OPTIONS environment variable to --stack-size=65536 and restart the Gateway.
• Consider reducing the depth of the ESM import chain for the affected plugins as a long-term solution to avoid similar issues.
• Alternatively, catching the error and skipping the plugin with a warning can prevent the Gateway from crashing.

Example

No code snippet is necessary in this case, as the solution involves environment variable changes and potential code optimizations.

Notes

The provided workaround requires a Gateway restart to take effect and may not be suitable for all environments. Reducing the import chain depth or setting a higher default stack size in the Gateway launcher may be more robust solutions.

Recommendation

Apply the workaround by setting NODE_OPTIONS=--stack-size=65536, as it provides a quick and effective solution to the issue, allowing the Gateway to function with the affected plugins.