“Bricked” after Reset — graphrag embedding RAM OOM

标题与摘要为原文，未翻译。

做了什么: Staff (deanrie, 2026-09-05): A “bricked” Agent Computer after heavy indexing can be graphrag embedding hitting the VM RAM ceiling (not disk)—Reset may take up to ~1 hour and re-clicking restarts the timer; after it returns, stop auto-indexing, check `free -h`, and run embedding/graph builds in smaller batches so memory stays under the limit (apt/pip outside working files need reinstall after Reset
场景: 写代码上线
怎么复制: 读原文：forum.cursor.com ↗
把原文里的步骤/提示词整理成一条消息交给 Bot
先手动跑一次，再决定频率
出处：https://forum.cursor.com/t/grokbot-bricked-wont-reset/170689
注意点: 这是一条额度/故障反馈（警告），不是可复制的作业。
Staff (deanrie, 2026-09-05): A “bricked” Agent Computer after heavy indexing can be graphrag embedding hitting the VM RAM ceiling (not disk)—Reset may take up to ~1 hour and re-clicking restarts the timer; after it returns, stop auto-indexing, check `free -h`, and run embedding/graph builds in smaller batches so memory stays under the limit (apt/pip outside working files need reinstall after Reset).
摘要整理自公开来源，以原文为准。