Uncaught Exception: TypeError: Object has been destroyed in BrowserWindow #30493

Activity

1. github-actions

   assigned

   Hona

   on Jun 3, 2026
2. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 3, 2026
3. github-actions commented on Jun 3, 2026

   

   github-actionsBot

   on Jun 3, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Required fields are missing: OpenCode version, Steps to reproduce, Operating System, and Terminal are all left as _No response_. Please provide this information so the issue can be investigated.
   • The description only contains a stack trace with no context about what you were doing when the error occurred, how to reproduce it, or how often it happens.

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Desktop: Uncaught TypeError: Object has been destroyed in main process (index.js:679) #29448: Same "TypeError: Object has been destroyed" error in the Electron desktop app main process

   If you believe this was flagged incorrectly, please let a maintainer know.
4. github-actions commented on Jun 3, 2026

   

   github-actionsBot

   on Jun 3, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for updating the issue with your OS and OpenCode version — that helps!

   However, this bug report still needs a bit more information before it can be investigated:

   • Steps to reproduce is still empty. Please describe what you were doing when this error occurred — for example, what action triggered it, how often it happens, or any steps that reliably reproduce it.

   Even a brief description like "this happens when I close the window while a session is loading" would be very helpful. Please edit the issue to add this context.
5. github-actions commented on Jun 3, 2026

   

   github-actionsBot

   on Jun 3, 2026 – with GitHub Actions

   Contributor

   More actions

   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.
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 3, 2026
7. github-actions

   closed this as not plannedon Jun 3, 2026