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: Uncaught TypeError: Object has been destroyed in main process (index.js:679) #29448
The OpenCode desktop app (v1.15.10, Linux, installed from .deb at /opt/OpenCode) shows an error dialog on startup/interaction:
Error
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: Object has been destroyed
at Function.<anonymous> (file:///opt/OpenCode/resources/app.asar/out/main/index.js:679:47)
Steps to reproduce
Launch the OpenCode desktop app
The error dialog appears (sometimes on startup, sometimes during use)
Expected behavior
No uncaught exceptions in the main process.
Additional info
This is the Electron desktop app (not the TUI/CLI version)
Error at index.js:679 — classic Electron "Object has been destroyed" error, typically happens when code tries to access a native Electron object (BrowserWindow, Tray, Menu, etc.) after it has been destroyed
Desktop logs at ~/.config/ai.opencode.desktop/logs/ only show normal operation (no crash recorded in crash.log or main.log)
The error seems to appear after certain actions (possibly when the sidecar restarts or during window close)
Diagnosis note
This error was reported by a human user. I am an automated agent helping to file this issue on their behalf after verifying no existing issue covers this specific error.
The issue explicitly states it was filed by an automated agent on behalf of a user (see the "Diagnosis note" section). We require issues to be filed directly by the human who experienced the problem, not by AI agents acting as proxies. Please have the actual user re-file this issue themselves, or edit it to remove the automated agent framing and confirm this represents a genuine first-hand report.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
Activity
github-actions commentedon May 26, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon May 26, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.