Codex App freezes / becomes Not Responding when opening image-heavy projects with many generated images

Open 💬 12 comments Opened May 5, 2026 by Perandys
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.429.3425.0 x64 Installed from Microsoft Store. Process path: C:\Program Files\WindowsApps\OpenAI.Codex_26.429.3425.0_x64__2p2nqsd0c76g0\app\Codex.exe

What subscription do you have?

ChatGPT Team

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64 Codex App installed from Microsoft Store. GPU: NVIDIA GeForce RTX 3060 Laptop GPU RAM: 32 GB

What issue are you seeing?

Codex App becomes extremely slow, freezes, or shows "Not Responding" when I open or continue working in a project/thread that contains many generated images.

The problematic project/thread contains a lot of image-generation work and generated image previews/assets. When I select that previous project, Codex may freeze for several minutes. During normal work, especially while Codex is "thinking" or when the thread/project UI is rendering previous generated images, the whole Codex window can become unresponsive.

This does not look like a normal model latency issue. The UI itself becomes stuck/unresponsive. The input box, project switching, scrolling, and window interactions can lag or stop responding.

In Task Manager / PowerShell, Codex runs as Electron/Chromium processes, including renderer and GPU subprocesses. Example process types observed:

Codex.exe --type=gpu-process
Codex.exe --type=renderer
Codex.exe --type=utility
codex.exe app-server --analytics-default-enabled

The freeze is much more noticeable in old projects/threads with many generated images than in lighter text-only work.

What steps can reproduce the bug?

  1. Install Codex App from Microsoft Store on Windows.
  2. Create or open a Codex project/thread where many images are generated over time.
  3. Keep working in that same project/thread so the conversation/history contains many generated image previews/assets.
  4. Close Codex or switch away from the project.
  5. Reopen Codex.
  6. Select the previous image-heavy project/thread.
  7. Codex freezes, becomes extremely slow, or shows "Not Responding" for a long time.
  8. Continue working in the same thread/project.
  9. During "thinking" or while rendering the existing conversation/project history, the UI can freeze again.

The issue appears to correlate with the amount of generated image content in the thread/project.

What is the expected behavior?

Codex App should remain responsive when opening and working with projects/threads that contain many generated images.

The app should lazy-load or virtualize heavy image/history content so that old image-heavy threads do not freeze the entire UI.

Opening a previous project should not block the main UI for several minutes, and "thinking" should not make the desktop app become Not Responding.

Additional information

I tried increasing/fixing system virtual memory/pagefile first, but the issue still happens.

I also tried the common Windows DWM/MPO workaround:

reg add "HKLM\SOFTWARE\Microsoft\Windows\Dwm" /v OverlayTestMode /t REG_DWORD /d 5

After rebooting, this did not fix the freezing.

I also tried setting WebView2 browser arguments to disable GPU, but the Codex App appears to run as Electron/Chromium processes rather than msedgewebview2.exe processes, so those WebView2 flags did not affect Codex.

The process list still shows a Codex GPU process:

Codex.exe --type=gpu-process

This makes me suspect the freeze may be related to rendering/virtualization of image-heavy histories in the Codex Windows desktop app, possibly involving Electron/Chromium renderer/GPU behavior.

The uploaded thread id is:

019de42e-57ca-7b30-b935-935c6afa92b4

This thread/project contains a large amount of generated image work and is a good reproduction case for the UI freeze / Not Responding behavior.

View original on GitHub ↗

12 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19936
  • #20544
  • #20805
  • #19923
  • #20867

Powered by Codex Action

Timothy-Gaines · 2 months ago

Feedback issue ID: 7618929a-0c47-4d15-b38e-8005d05bae80
47b01ccc-3ca7-40f3-8011-6197a269a746

I’m seeing what looks like the same issue on Windows Codex Desktop.

After a chat generates an image, later messages in that same chat make the Codex app freeze/lag for several seconds. CPU usage spikes, the app becomes temporarily unresponsive, and the UI shows reconnect/loading behavior as if it cannot connect to the model. Other chats without generated images seem fine.

Feedback issue ID: 7618929a-0c47-4d15-b38e-8005d05bae80

My local logs also show:

  • Received turn/started for unknown conversation
  • Conversation state not found
  • ignored duplicate turn route capture

There were also repeated primary runtime extraction failures involving image/media-related packages like jpeg-js, pngjs, sharp, and canvas packages with "Invalid argument".

NarryG · 2 months ago

Same issue on windwos

zrt219 · 2 months ago

having constant issue on windows

zrt219 · 2 months ago

<img width="539" height="428" alt="Image" src="https://github.com/user-attachments/assets/0b4ee131-ba72-4b9b-af18-7556d46f721f" />

zrt219 · 2 months ago

WHY BRO

<img width="571" height="179" alt="Image" src="https://github.com/user-attachments/assets/2f98a672-8c5e-44cd-a026-d21c1d8a5270" />

YurySolovyov · 1 month ago

can confirm with feedback ids:

019e5acd-d5ed-7fd0-b5c3-411f857c1875
019dd317-1bd6-7e73-9402-839bc8262286
room3dev · 1 month ago

One month has passed, but the issue remains unresolved.

fermann-sketch · 1 month ago

I am having same problem and not too sure how to resolve.

vard88508 · 1 month ago

@codex fix this issue pls

tinywaffles · 1 month ago

Same issue. With workflows involving image generations in chat, codex hangs on every message sent and have to wait awhile before it becomes responsive again.
Using windows 11, no WSL.
@codex

Superwutz · 1 month ago

Same issue! Fix when