Renderer unresponsive (freezes) with Solid.js findDOMIndex infinite loop - OpenCode 1.16.2 #31099

Bug Description

OpenCode desktop v1.16.2 renderer process becomes unresponsive after ~12 minutes of use. The window freezes and shows "renderer unresponsive" in the window log.

Environment

• OpenCode version: 1.16.2 (packaged)
• Platform: macOS (darwin, arm64)
• Electron: 41.2.1 (Chrome 146)
• Node: 24.14.1

Stack Trace

The hang occurs in the Solid.js reactivity system, specifically in findDOMIndex during registerItem → findDOMIndex → setValue → completeLoad:

at findDOMIndex (main-CMia5thD.js:85569:3)
at main-CMia5thD.js:85670:21
at accessWith (main-CMia5thD.js:8340:44)
at setValue (main-CMia5thD.js:9594:5)
at Object.registerItem (main-CMia5thD.js:85669:5)
at Object.fn (main-CMia5thD.js:85706:32)
at runComputation (main-CMia5thD.js:487:22)
at updateComputation (main-CMia5thD.js:470:3)
at runTop (main-CMia5thD.js:566:7)
at runUserEffects (main-CMia5thD.js:660:39)
at completeLoad (main-CMia5thD.js:167:5)

Full debug dump exported at the time of the freeze is available.

Steps to Reproduce

1. Start OpenCode desktop v1.16.2
2. Use normally (chat, code edits, etc.)
3. After ~12 minutes the UI freezes
4. Eventually the OS shows "renderer unresponsive" dialog

Additional Observations

• This happened across multiple sessions (at least 2 consecutive sessions)
• The ResizeObserver warning appears in renderer log before the freeze
• There is a pending Crashpad minidump at ~/Library/Application Support/ai.opencode.desktop/Crashpad/pending/0d103bb8-9d9c-459a-9b6b-5c8fc368ea1f.dmp (900KB) if needed for debugging

Related Server Errors

The server also logs repeated ENOENT errors when a configured workspace path (/Users/timmy/writing-plotter-cad-test/plotter_console) does not exist on disk - but this may be unrelated to the renderer hang.