Grok Bot computer is experiencing high CPU steal and I/O stalls, leading to slow performance despite being mostly idle

Signals over time

3 observed signals across 1 sources, tracked for 7 days. Confidence: low.

What people are saying Observed

• “Grok Bot shared computer at ~12 of 16 GB RAM right after restart, platform processes, overnight crash and connectors logged out. Hi team, My Grok Bot computer (16 GB, 8 cores, no swap) keeps running out of memory and getting very slow, even when no bot is doing real work. What I see Right after a restart, about 12.3 of 16 GB is already in use, and that is with no workloads running. I cut my bots from 55 to about 34, and it barely helped. Snapshot from 13 Oct, 11:33 CEST: 79 node processes use about 5 GB. That includes sand-host/host-main.cjs at about 950 MB and one exec-daemon serve per agent at 100 to 150 MB each, plus the playwright runtimes. 26 chrome processes use about 3.3 GB. One browser profile was still alive 3h40 after its task had finished. 9 per-agent desktop stacks (Xvfb, plank, xfwm4, x11vnc, bamfdaemon) use about 1.7 GB. About 90 box-bounded-log processes are running (yesterday there were 163, about 2.2 GB, so it looks like a leak), plus dozens of flock and bash wrappers and a few zombie processes. Yesterday the load hit 146 on 8 cores with 13 of 15 GB in use. A scheduled overnight routine failed at 02:49, and the computer restarted on its own around 04:50. After “Upd”

  RSS Feeds · complaint

• “Grok Bot computer freezes/reboots repeatedly and kills 24/7 background scripts. Where does the bug appear (feature/product)? Grok Bot Describe the Bug My Grok Bot runs a 24/7 pipeline on its own computer: bash scripts collect data every 30 minutes and wake a webhook routine to publish. The bot computer keeps freezing for long periods, and once it rebooted. While it is frozen, all background processes stop, so scheduled ticks are missed and data is lost. After the reboot all user processes were gone and did not start again on their own. Observed (Asia/Yekaterinburg, UTC+5), Oct 9–10, 2026: Freezes: ~20:44–22:01, 22:32–22:46, 22:49–01:03, 01:20–07:38, 08:00–11:12, 11:48–14:21, 19:31–21:25 Reboot: Oct 10 ~16:53, background scripts killed Steps to Reproduce On the Grok Bot computer, start long-running background scripts (nohup bash loops with sleep, logging a line every 30 min). Leave the bot idle for an hour or more. Check the logs: there are gaps of 15 minutes to 6 hours with no entries. The processes are still listed afterwards but did not run during the gap. Sometimes the computer reboots and all user processes are gone. Expected Behavior The bot computer stays awake while user bac”

  RSS Feeds · complaint

• “Grok Bot computer very slow: high CPU steal and I/O stalls while idle. Where does the bug appear (feature/product)? Grok Bot Describe the Bug My Grok Bot computer has been very slow since this morning even though it’s mostly idle. What I’m seeing: Load average is 35 to 70 on 8 cores, but only about 4 processes are running. vmstat shows CPU steal (st) up to 36%, while user plus system time is only 1 to 13%. I/O pressure (full avg10) is around 22%, with almost no local disk traffic. Memory is fine: 5 GB free, no swap in use. Both Chrome browsers on the computer have stopped responding. Uptime is about 46 hours. I already ran “Update Grok Bot’s Computer.” That fixed my disk size (now 126 GB) but not the slowness. This looks like a busy host or slow underlying storage, not something running on my computer. Can you move my computer to a less busy host or check the storage? I rely on it for scheduled recordings, so I need it stable today. Steps to Reproduce Grok Bot computer has been running about 46 hours, mostly idle (no bots recording). Run uptime, vmstat 1 5, and cat /proc/pressure/io on the agent computer. Load average shows 35 to 70 on 8 cores while only about 4 processes are runni”

  RSS Feeds · complaint