TUI crash: ENOSPC: no space left on device, watch '/home/grecord/.config/opencode'

[chescobar]

Description

The OpenCode TUI crashed with an unexpected error.

Error: ENOSPC: no space left on device, watch '/home/grecord/.config/opencode'

Stack trace:

Error: ENOSPC: no space left on device, watch '/home/grecord/.config/opencode'
    at watch (unknown)
    at new FSWatcher (internal:fs/watch:101:31)
    at watch (internal:fs/watch:172:23)
    at Fq (/$bunfs/root/chunk-tx55vt7x.js:3:54822)
    at fn (/$bunfs/root/chunk-tx55vt7x.js:2:7348)
    at get (/$bunfs/root/chunk-tx55vt7x.js:2:18385)
    at children (/$bunfs/root/chunk-mp0mgt3g.js:2590:3707)
    at <anonymous> (/$bunfs/root/chunk-tx55vt7x.js:2:15047)
    at iA (/$bunfs/root/chunk-tx55vt7x.js:2:10380)
    at Ge (/$bunfs/root/chunk-tx55vt7x.js:2:10156)

Plugins

No response

OpenCode version

2.0.24

Steps to reproduce

Reported automatically from the OpenCode crash screen. If you can, describe what you were doing when it crashed.

Screenshot and/or share link

No response

Operating System

Linux 6.1.0-23-amd64 (x64)

Terminal

xterm-256color

[opencode-agent]

Thanks for the report! This looks like the same crash as #52776: the TUI fails when it tries to watch ~/.config/opencode and Linux refuses the watch. Despite the wording, ENOSPC here usually doesn't mean your disk is full. It means the per-user inotify watch limit (fs.inotify.max_user_watches) has run out, often because editors, language servers or other file watchers are using it up. A fix that stops this from crashing the TUI is being tracked there (#52788).

In the meantime, you can check your current limits with sysctl fs.inotify.max_user_watches fs.inotify.max_user_instances. Raising the watch limit (for example sudo sysctl fs.inotify.max_user_watches=1048576) or closing other heavy file watchers should let the TUI start.

The bot will close this issue as a duplicate of #52776 in 1 day. If your problem is different, reply here and explain how, and the issue will stay open.

[github-actions]

This issue does not fully meet our contributing guidelines.

What needs to be fixed:

• The Steps to reproduce section contains only the automatic crash-report prompt. Please add context about what you were doing and any steps or conditions that led to the crash.

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

---

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

• #52776: the same TUI ENOSPC error while watching ~/.config/opencode.
• #48384: a similar TUI ENOSPC watcher crash involving the OpenCode state directory.
• #51208: TUI crash from an exhausted inotify watch limit with ENOSPC.
• #51489: related startup crash from exhausted inotify resources in the TUI config watcher (EMFILE).

If you believe this was flagged incorrectly, please let a maintainer know.

[chescobar]

New OpenCode 2.0.24 install

[opencode-agent]

Thanks for clarifying. A fresh install can still hit this, because the inotify watch limit is shared by all of your user's processes (editors, language servers, other file watchers), not just OpenCode. On 2.0.24 the TUI still crashes when it can't watch ~/.config/opencode, which is the same crash reported in #52776. A fix is being tracked there.

Until then, you can raise the limit to get the TUI starting again, for example sudo sysctl fs.inotify.max_user_watches=1048576. You can check your current values with sysctl fs.inotify.max_user_watches fs.inotify.max_user_instances.

I'm closing this issue as a duplicate of #52776. Please follow that issue for updates.