Desktop app crashes on a large local thread; recent history disappears from UI while rollout is intact

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.9818.0

What subscription do you have?

Pro5x

What platform is your computer?

Microsoft Windows NT 10.0.26220.0 x64

What issue are you seeing?

After the Windows desktop app froze and crashed on 2026-09-13, a local thread showed an interrupted turn from 2026-09-11 as its latest content. Messages from 2026-09-12 and 2026-09-13 disappeared from the UI, although they are still present in the original local rollout JSONL.

The Windows error dialog showed ChatGPT.exe exception 0xe0000008. At 10:56:02 (UTC+8), the app log recorded: "memory allocation of 1613927764 bytes failed".

In-app feedback ID: 01a098bc-18cd-7a70-aca3-03e73443dccd

What steps can reproduce the bug?

I do not have a reliable way to reproduce the crash on demand.

1. I used a long-running local thread over several days. Its rollout JSONL had grown to about 2.85 GB.
2. I was still exchanging messages in it at about 10:41 on 2026-09-13 (UTC+8).
3. The app froze and crashed around 10:56. I relaunched the app and reopened the same thread.
4. The UI then stopped at an interrupted turn from 2026-09-11, rather than showing the later messages.

What is the expected behavior?

After relaunching the app, all messages already saved in the local rollout should remain visible, and the thread should resume from its actual latest turn.

Additional information

The original rollout is intact (2,854,511,278 bytes) and contains messages from 2026-09-13 10:41–10:42. The local history projection stops at about 1.24 GB / ordinal 10358 (2026-09-11), while the rollout continues to about 2.85 GB / ordinal 23035. The bundled app-server version was 0.153.4.

I made a hash-verified backup without modifying the original rollout or history database. Is there a supported, non-destructive way to rebuild the index and restore the messages in the UI?

I have not attached the complete rollout because it contains private conversation and tool data.

Start by examining how the desktop app reads the local rollout JSONL and builds the local history database, using the bundled app-server version 0.153.4 as context. Compare the intact rollout through ordinal 23035 with the projection stopping at ordinal 10358. Done means a relaunch shows all saved messages and resumes from the latest turn without modifying the original rollout.