High CPU Usage & FileWatcher TimeoutError on Startup (Opencode Desktop)

[KleirRampage45]

Description

When launching opencode-desktop, the application immediately consumes excessive CPU resources, even when no project or workspace is loaded. Terminal logs show the file.watcher service timing out while attempting to subscribe to /home/USER and the root directory /. NOTE: this is on a high end system with a 7800X3D cpu, and its by far the most taxing IDE/agent that ive tested, this does not happen with Cursor, codex or antigravity. The CPU usage does not go down with time, 30 minutes can go by and it will still be using significant CPU resources and keep fans running.

Plugins

n/a

OpenCode version

1.4.6-1 (Installed via AUR: opencode-desktop-bin)

Steps to reproduce

1. Open Terminal
2. Run opencode-desktop
3. Observe TimeoutError in logs and immediate CPU spike in system monitor.

Screenshot and/or share link

Note that my root / shows as a recent project opened (never created one at root or home)

memory leak maybe? too much ram usage for a program thats supposed to be at idle.

Operating System

Linux 6.19.11-arch1-1

Terminal

Konsole

[github-actions]

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

• File watcher subscription timeout on network-mounted drives #20722: File watcher subscription timeout — same failed to subscribe / TimeoutError symptom on startup
• Snapshot can recursively ingest its own data when worktree is the home directory #20442: Snapshot recursively ingesting home directory data — directly related to root / and /home/USER being treated as worktrees, causing high CPU and disk activity
• opencode is using CPU for doing nothing! #19466: OpenCode using CPU for doing nothing — similar high idle CPU symptom

[KleirRampage45]

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

• File watcher subscription timeout on network-mounted drives #20722: File watcher subscription timeout — same failed to subscribe / TimeoutError symptom on startup
• Snapshot can recursively ingest its own data when worktree is the home directory #20442: Snapshot recursively ingesting home directory data — directly related to root / and /home/USER being treated as worktrees, causing high CPU and disk activity
• opencode is using CPU for doing nothing! #19466: OpenCode using CPU for doing nothing — similar high idle CPU symptom

Not the same issue, none mention file indexing the root directory or filewatcher timeout. Not duplicated.

[NicolasSFPD]

I have the same behaviour (using opencode desktop 1.4.7).

As soon as I launch OpenCode desktop; it's sub-process "opencode-cli" burns one CPU constantly.
And I also have the sidecar error logs for several folders (might mean the CPU load is related to file.watcher mechanism, but unsure).

For info, the folders for which it gives that file.watcher TimeoutError:

• $HOME
• $HOME/development/git/myFirstRepo
• $HOME/development/git/mySecondRepo
• $HOME/development/git/myFirstRepo/.git
• $HOME/development/git/mySecondRepo/.git

Its Also worth noting that if I launch "opencode-cli" directly (not the desktop version) for one of my repos, I do not have that issue.

For more context, I'm using Fedora 43 with KDE.

[KleirRampage45]

I have the same behaviour (using opencode desktop 1.4.7).

As soon as I launch OpenCode desktop; it's sub-process "opencode-cli" burns one CPU constantly. And I also have the sidecar error logs for several folders (might mean the CPU load is related to file.watcher mechanism, but unsure).

For info, the folders for which it gives that file.watcher TimeoutError:

• $HOME
• $HOME/development/git/myFirstRepo
• $HOME/development/git/mySecondRepo
• $HOME/development/git/myFirstRepo/.git
• $HOME/development/git/mySecondRepo/.git

Its Also worth noting that if I launch "opencode-cli" directly (not the desktop version) for one of my repos, I do not have that issue.

For more context, I'm using Fedora 43 with KDE.

Also using KDE. Would be nice to know if anyone else using linux with the same or another DE is having these issues.