Windows desktop app exits unexpectedly after memory-leak and hang events

Start by reviewing the desktop logs around the abrupt stop and the Windows Error Reporting evidence for RADAR_PRE_LEAK_64 and AppHangTransient. Compare the reported conversation-state and ResizeObserver messages with the expected behavior, then determine whether the desktop shell can recover a failed renderer or background component instead of exiting silently. Done means the failure cause is identified and the app remains open or presents an error when a component fails.

Summary

The Codex desktop app on Windows intermittently becomes unresponsive or exits completely while tasks are running. This is an application-process exit, not merely an interrupted model response.

Environment

• Codex Windows app package: OpenAI.Codex 26.721.4979.0 (Microsoft Store package)
• Windows 11 Pro, version 10.0.26200
• App executable recorded by Windows: ChatGPT.exe
• Chromium executable version recorded in WER events: 150.0.7871.124 / 150.0.7871.128

Observed behavior

• The app can disappear while one or more Codex tasks are active.
• Reopening the app starts an entirely new set of ChatGPT.exe processes.
• Desktop logs from the previous process stop abruptly, without a normal shutdown sequence.
• Shortly before one abrupt stop, the desktop logs repeatedly contained messages such as:
  • Conversation state not found
  • Received item/started for unknown conversation
  • Received item/completed for unknown conversation
  • ResizeObserver loop completed with undelivered notifications

Windows Error Reporting evidence

Windows Event Viewer recorded the following events for ChatGPT.exe:

1. RADAR_PRE_LEAK_64 (memory-leak detection)
2. AppHangTransient (application hang)

The leak event occurred before the later hang event. There was ample free system memory at the time of inspection, so this does not appear to be simple system-wide RAM exhaustion.

Expected behavior

The app should remain open while tasks are active. If a renderer or background component fails, the desktop shell should recover it or present an error instead of silently exiting.

Privacy note

Raw application logs and session transcripts are intentionally not attached because they may contain local paths, project names, or conversation content. A redacted excerpt or WER report ID can be provided privately if maintainers request it.