抄作业 / 做成了什么 / Grok Bot

做了什么

Staff (deanrie, 2026-09-05): Quiet Windows launch crash (int3 / 0x80000003) is often AppData\Local install ACLs left by CodexSandboxUsers without ALL RESTRICTED APPLICATION PACKAGES (S-1-15-2-2)—`--disable-gpu`/`--jitless` won’t help; diagnose with `--disable-gpu-sandbox`, then `icacls` grant S-1-15-2-1/2 (RX) on the Grok Bot folder (and optionally `%LOCALAPPDATA%\Programs`) or remove the orphaned

场景

写代码上线

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• — 截图 / 媒体来源未提供
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

— 表示来源没有给出，本站不补写。

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot crashes on every launch, about 1 second after start, before any UI appears. 1–3 processes flash in Task Manager and vanish. No window, no error dialog. 100% reproducible. The GPU child process exits with code -2147483645 (STATUS_BREAKPOINT / 0x80000003). The whole app then tears down. WinDbg on the Crashpad dump shows a literal int3 (0xCC) executing inside V8 JIT-generated code in the main window process. Exception offset is Grok_Bot+786cdd6. Same offset on 0.28.0 and 0.43.0. App-level code changed between those

展开全文

builds. The bundled Electron/Chromium/V8 runtime did not. This is a runtime defect, not app logic. Steps to Reproduce • Install official Windows x64 Grok Bot (tried 0.28.0 and 0.43.0). • Launch from Start menu or desktop shortcut. • Processes appear for ~1 second, then all exit. No UI. …

摘自论坛首帖，照录原文，未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下