You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Desktop: legacy layout freezes when switching projects #39141
Switching projects from the left project rail can freeze OpenCode Desktop when the legacy layout is active. The window stops responding and must be restarted.
The renderer log records this at the freeze:
Uncaught (in promise) TypeError: Cannot read properties of null (reading '0')
A Chrome DevTools Protocol capture at the failure showed repeated SolidJS cleanNode frames. The owner chain pointed to the accepting memo in the legacy PromptInput:
This appears to be re-entrant Solid cleanup while the project/session subtree is being disposed. It resembles the Solid issue addressed by solidjs/solid#2062.
Plugins
No response
OpenCode version
Desktop 1.18.7
Steps to reproduce
Disable New layout designs so the legacy layout is active.
Open a project with an existing session.
Switch to another project from the left project rail.
Repeat if necessary; the renderer freezes and logs the null-property exception.
This issue might be a duplicate of existing issues. Please check:
[Bug]: Desktop v1.18.4 ResizeObserver loop + UI freeze also affects old layout (not only v2) #37997: Desktop v1.18.4 UI freeze also affecting the legacy layout (similar symptom: renderer becomes unresponsive and must be restarted); the root cause reported there is a ResizeObserver feedback loop rather than the SolidJS cleanNode re-entrancy described here, but both target the legacy layout under Desktop on Windows.
Activity
github-actions commentedon Jul 27, 2026
This issue might be a duplicate of existing issues. Please check:
cleanNodere-entrancy described here, but both target the legacy layout under Desktop on Windows.github-actions commentedon Sep 26, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.