OpenCode desktop v1.18.10 - V8 OOM 'Zone Allocation failed' when opening project #39825

Title: OpenCode desktop v1.18.10 — V8 OOM "Zone Allocation failed" when opening project (server OOM, renderer "Failed to load sessions")

Environment

• App: OpenCode Desktop v1.18.10 (darwin)
• OS: macOS
• Repo: a local code repository (opened at the workspace root)

Summary
When opening the repository (or on startup), OpenCode's embedded server process repeatedly hits V8 OOM ("Zone Allocation failed") and the renderer shows repeated "Failed to load sessions — TypeError: Failed to fetch". This renders the app unusable; restarting or removing sessions/Crashpad provides only temporary relief.

Reproduction steps

1. Install and open OpenCode Desktop v1.18.10 on macOS.
2. Open the workspace root for this repository (or allow the app to index the project).
3. Observe in Help → Toggle Developer Tools → Console: repeated "Failed to load sessions" errors. Check server logs for V8 OOM traces.

Observed behavior

• server.log contains repeated GC traces ending in: "OOM error in V8: Zone Allocation failed - process out of memory".
• renderer.log repeats: "Failed to load sessions TypeError: Failed to fetch".
• Increasing V8 heap (NODE_OPTIONS=--max-old-space-size=4096) did not prevent the OOM.

Attachments included

• Server and renderer logs plus minimal app state (packaged as a zip)

Relevant GC trace (excerpt)

• The server log contains multiple recent GC traces showing large heap sizes and allocation failures, for example: "<--- Last few GCs ---> ... Scavenge ... allocation failure; Incremental Mark-Compact ... -> ... MB ... ERROR: OOM error in V8: Zone Allocation failed - process out of memory". (Process IDs and timestamps removed for privacy.)

Notes

• I attempted removing Crashpad and logs and relaunching; the problem recurred shortly after.
• The repo itself is not large; I added workspace excludes and redirected Bundler installs away from vendor/bundle to rule out repo-size induced indexing.
• Increasing --max-old-space-size did not prevent the OOM.

Please advise next steps or confirm if this should be escalated to a crash/GC fix in Electron/V8.

opencode_bug_v1.18.10_sanitized.zip