抄作业 / 做成了什么 / Grok Bot
Forum: Grok Bot's own host process filling the computer's memory
标题与摘要为原文，未翻译。
- 做了什么
- Report that the app's host process on a Bot Computer held about 15 GB of 16 GB RAM from 7 Oct, so commands were killed or hung and Update said it was current; staff confirmed it, said Reset is the way out because it restores the last snapshot saved minutes before, and passed the leak to the team as it recurred on a fresh computer.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Describe the Bug The app’s own background process is using about 15 GB of 16 GB on Grok Bot’s computer, every command gets killed for running out of memory, it’s been like this since this morning (and last night), and Update says it’s already on the latest version. The process is node /opt/sand/sand-host/host-main.cjs, the app’s own host process. It holds about 15 GB of the box’s 16 GB of RAM, leaving roughly 150 to 290 MB free with no swap. Load average is 40 to 60 on 8 CPUs. The kernel’s out-of-memory killer keeps killing small processes like Xvfb, python3 and node, but never the leaking
展开全文
process, which is shielded from being killed. It started around 8:30 AM CT on Oct 7 and hasn’t recovered since. A similar leak happened on Oct 6 after a system update. Commands fail with “Service temporarily unavailable” or hang for minutes. Even free -m didn’t finish in over a minute. …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下