Summary

• Wrap JSON.stringify in adapter emit() with try-catch to prevent RangeError: Invalid string length when data payloads exceed V8's string size limit
• Log the error and return early instead of crashing with an unhandled promise rejection
• Also avoids redundant JSON.stringify calls per window by serializing once before the loop

Sentry Issue

ELECTRON-D9 — RangeError: Invalid string length in src/common/adapter/main.ts:39

• 6 occurrences, last seen 2026-03-30
• Triggered by oversized data passed to bridge.adapter.emit() → JSON.stringify({ name, data })
• Release: [email protected]

Root Cause

JSON.stringify throws RangeError: Invalid string length when the resulting string would exceed ~512 MB (V8 limit). The adapter's emit function called JSON.stringify without error handling, causing an unhandled promise rejection that crashed the event broadcasting.

Fix

1. Serialize once before the window loop (also a minor perf improvement — avoids re-serializing per window)
2. Catch serialization errors and log them with console.error
3. Return early on failure — skip both IPC send and WebSocket broadcast

Test Plan

• Added test case in tests/unit/adapterEmitGuard.test.ts that mocks JSON.stringify to throw RangeError and verifies:
  • No exception propagates
  • win.webContents.send is not called
  • broadcastToAll is not called
  • Error is logged to console
• All existing adapter tests pass (5/5)
• Type check passes (bunx tsc --noEmit)
• Lint passes (0 errors)