openclaw - 💡(How to fix) Fix [Bug]: MiniMax fetch blocks Node.js event loop for ~135s → watchdog SIGTERM (regression in v4.27) [1 comments, 2 participants]

TL;DR

The most likely fix involves addressing the synchronous operation in the MiniMax provider by moving it off the main thread and implementing a timeout for the fetch call.

Guidance

• Identify and refactor the CPU-bound synchronous operation in the MiniMax provider to run on a worker thread or use an asynchronous approach to prevent blocking the event loop.
• Implement AbortSignal.timeout() for the fetch call at src/agents/minimax-vlm.ts:81 to prevent indefinite waits when the MiniMax API is unresponsive.
• Review related issues (#54142 and #74728) for additional context and potential fixes.
• Consider testing with a smaller input or a mock API to isolate the issue and verify the fix.

Example

// Example of using AbortSignal.timeout() for the fetch call
const controller = new AbortController();
const signal = controller.signal;
const timeoutId = setTimeout(() => controller.abort(), 30000); // 30-second timeout

fetch('/v1/coding_plan/vlm', { signal })
  .then(response => {
    clearTimeout(timeoutId);
    // Process the response
  })
  .catch(error => {
    if (error.name === 'AbortError') {
      console.log('Fetch timed out');
    } else {
      console.error('Fetch error:', error);
    }
  });

Notes

The provided workaround of reverting to v2026.4.26 may not be a long-term solution, and addressing the root causes (Issue A and Issue B) is necessary for a stable fix.

Recommendation

Apply a workaround by implementing AbortSignal.timeout() for the fetch call and refactoring the synchronous operation in the MiniMax provider to run asynchronously, as this addresses both identified issues and prevents event loop blocking.