Fix Grok Bot Chrome OOM / Error code 9 on the shared computer

Every Bot on your account shares one cloud computer with a fixed amount of RAM. Cursor staff (kevinn) on Agent Computer unreachable after Update / Recover / Reset diagnosed a common failure: several agents running browser work at once fill that RAM, Chrome starts dying with Error code 9, and a crash can drop a site back to its sign-in page.

Staff treat it as shared-computer memory pressure. A healthy gateway can still show Chrome crashes, and hammering Update / Recover / Reset from Settings will not free the RAM.

What it looks like

• An “Aw, Snap!” / crash page inside the Bot’s browser (not your laptop Chrome).
• Staff example: ~127 Chrome processes across agents using ~16.5 GB on a ~15 GB machine, with only a few hundred MB free.
• A Bot that was signed into a site is suddenly back on the login screen after a crash.
• Chat may still work while computer-use browser tabs keep dying.

What to try before Reset

1. Ask the Bot to close extra browser tabs and finish or stop other agents that are also browsing.
2. On the Bot’s screen, click Reload on the crashed tab, or tell the Bot to reload the page.
3. If the Bot is not answering at all, fully quit Grok Bot (macOS: Cmd+Q) and reopen. Staff: do not run Update, Recover, or Reset for a Chrome crash when the computer itself is healthy.
4. Sign back into the site that lost its session after the crash.

When staff has to rebuild

If browser work keeps OOM-crashing the shared computer after you thin the tabs, open Send Feedback with the Bot name, approximate time, and what you see. On the same thread, staff rebuilt the computer from the backend, restored memory to normal, and kept files, bots, and prior work intact — the user only had to sign into the site again.

Client-side Reset while Chrome is thrashing can make things worse without freeing the real cause.

Pitfalls

• All of your Bots share one machine. Parallel browser scrapes stack on the same RAM pool — see Do Grok Bots share one computer.
• A long Reset after a heavy embed job is a different path: Fix Grok Bot RAM OOM when Reset is slow.
• “Can’t reach your computer” after Update / Recover / Reset all fail is another path: When client Update, Recover, and Reset all fail.