opencode crashes on startup when SQLite database is corrupted #37821

Activity

1. github-actions

   assigned

   rekram1-node

   on Jul 20, 2026
2. github-actions commented on Jul 20, 2026

   

   github-actionsBot

   on Jul 20, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • opencode crashes on start with SQLITE_CORRUPT #30157: opencode crashes on start with SQLITE_CORRUPT — same error, same crash-on-startup behavior
   • SQLite database corruption (database disk image is malformed) when running concurrent sessions on NFS #14970: SQLite database corruption ("database disk image is malformed") — same error message, includes workaround and suggested fixes
3. B67687 commented on Aug 3, 2026

   

   B67687

   on Aug 3, 2026

   Contributor

   More actions

   Confirmed on our side (opencode v1.18.11, Linux, 2026-08-02)

   Same crash: opencode aborted natively (SIGABRT, 'core dumped') at startup, silently — no log line, no journal, no apport entry. Every dying instance stopped right after the boot line 'booting location services' (session-list/storage init, where a pathological DB/WAL gets read).

   Root cause chain on our machine:

   1. Shared SQLite store (WAL mode) grew to 5.45GB main + 5.48GB WAL because a runaway agent loop wrote unbounded into it (silent retry loop, ~94% CPU, 2h).
   2. New instances opened that DB → native abort at 'booting location services', intermittently, depending on DB state at launch.

   This is storage-layer corruption/bloat, not app logic — which is exactly why it was silent: the native abort happens below the JS layer.

   What fixed it for us

   • PRAGMA wal_checkpoint(TRUNCATE) + VACUUM (reclaimed ~1.7GB freelist, page_count 1,330,391 → compacted) + killed the runaway writer. DB 3.6GB, integrity ok, WAL 4KB, boot clean.

   Request

   A startup recovery path would have prevented the crash entirely: on open of a pathological/oversized DB, checkpoint or rebuild-in-place instead of native abort. #37822 (auto-recover) covers the right direction — hope it ships soon. Happy to attach core data or reproduce on request.
4. github-actions commented on Oct 3, 2026

   

   github-actionsBot

   on Oct 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as not plannedon Oct 3, 2026