4 people reported
All time, since Oct 8.
Hidden window resume loop
“maybe_resume_skipped_inactive_hotkey_window”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9297/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Hidden window resume loop pins renderer CPU on macOS. A stale ACTIVE heartbeat targeting a missing chat floods logs with maybe_resume_skipped_inactive_hotkey_window; some reports end in CrBrowserMain SIGTRAP crashes.
Is this your bug?
File my report- Where
- Desktop app renderer
- Error text
maybe_resume_skipped_inactive_hotkey_window- Versions
- 26.1002.52244
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Related: macOS desktop app SIGTRAP crashes
Not quite your bug?
- Chrome_IOThread SIGTRAP crash3 people
- Renderer crash opening sessions3 people
- Desktop app crashes mid-task3 people
Original reports4, newest first
- macOS: stale heartbeat causes unbounded hidden-window resume retriesOn GitHub#52533
- [macOS] Renderer stays above 100% CPU while idle; thousands of maybe_resume_skipped_inactive_hotkey_window eventsOn GitHub#52421
- [Codex App/macOS M1 8GB] High-CPU hidden renderer resume loop stops after pausing an old heartbeatOn GitHub#52185
- macOS: repeated CrBrowserMain SIGTRAP crashes with ~7,800 inactive-window resume messages/secOn GitHub#52091