Server main process OOMs at ~3.9 GB heap (feedback-monitor.js MODULE_TYPELESS_PACKAGE_JSON), sidecar exits clean (code 0), renderer bootstrap fails — v1.18.14 win32

Environment

• opencode version: v1.18.14 (packaged)
• Platform: win32 x64
• Node: 24.15.0
• Electron: 42.3.3
• Chrome: 148.0.7778.218
• userData: C:\Users\majq1\AppData\Roaming\ai.opencode.desktop
• Repro run: logs\20260825T015102 (and prior 20260825T014530)

Summary

The server/main process runs out of memory (V8 heap OOM at ~3.96 GB) shortly after startup, the bundled sidecar exits cleanly with code: 0, and the renderer can no longer reach the sidecar (ERR_CONNECTION_RESET / ERR_CONNECTION_TIMED_OUT), so the UI bootstrap fails with TypeError: Failed to fetch → "Failed to finish bootstrap instance".

A likely contributing factor appears in server.log before the crash: a MODULE_TYPELESS_PACKAGE_JSON warning pointing at a custom plugin file:///D:/opencode/config/plugins/feedback-monitor.js.

Key evidence (verified from the attached debug zip)

server.log — V8 heap OOM, and a warning about a local plugin just before crash:

[MODULE_TYPELESS_PACKAGE_JSON] file:///D:/opencode/config/plugins/feedback-monitor.js
...
CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
<--- Last few GCs --->
...
[3955:0x...]    39559 ms: Mark-sweep (...) ... 3962.4 (4101.9) -> 3955.2 (4103.9) MB, 118.1 / 0.0 ms  (average mu = 0.316, current mu = 0.213) allocation failure; scavenge might not succeed

renderer.log — bootstrap cannot reach the sidecar:

TypeError: Failed to fetch
...
fatal: Failed to finish bootstrap instance

main.log — sidecar connections drop:

net::ERR_CONNECTION_RESET  url: http://127.0.0.1:12493/...
net::ERR_CONNECTION_TIMED_OUT  url: http://127.0.0.1:9615/...

utility.log — sidecar exits cleanly (not a crash):

[warn] (utility) sidecar exited { code: 0 }

Notes

• Debug zip (session logs + crashpad .dmp) is on local disk only and could not be attached via API:
  D:\backup\user1\majq\Downloads\opencode-debug-20260825T015309.zip
• Sidecar exit code: 0 suggests the OOM in the main process tears it down rather than the sidecar itself crashing.
• Related open issues checked but bodies were unreadable: #41964, #35090, #44475.

Steps to reproduce

1. Launch the packaged opencode desktop app (v1.18.14) on Windows with the plugin dir D:\opencode\config\plugins present (contains feedback-monitor.js).
2. Wait for startup / a short session.
3. Observe the OOM in server.log, the sidecar exit, and the renderer bootstrap failure.