Codex App crashes reliably when opening new tab then navigating back in the in-app Browser

Open 💬 2 comments Opened Jun 7, 2026 by dansanduleac

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

Codex Desktop 26.602.40724 (3593)

What subscription do you have?

Pro 20x

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Codex App reliably crashes when opening a new tab from the in-app browser, then pressing the browser's back button.
Attached a redacted MacOS crash report.

Crash summary:
EXC_BREAKPOINT (SIGTRAP)
Triggered by Thread 0: CrBrowserMain
Codex Framework 149.0.7827.54
macOS 26.5 (25F71)
Apple Incident Identifier (if helpful): 93435558-9131-4F22-9883-AA3C0FAC60AF

codex-iab-back-crash-redacted.txt

What steps can reproduce the bug?

Open a page in the Codex in-app Browser.
Click a link that normally opens in a new tab/window.
Codex opens it in the same in-app browser view because there is no multi-tab UI.
Press the in-app Browser back button.
Codex crashes a few seconds afterwards.

What is the expected behavior?

No crash, navigate back to the original tab.

Additional information

_No response_

View original on GitHub ↗

2 Comments

liby · 2 months ago

Adding a macOS data point from Codex Desktop 26.608.12217 (build 3722), Codex Framework 149.0.7827.54, on macOS 26.5.1 (25F80), Apple Silicon.

This is not the exact back-button reproduction from the issue body, but the crash signature looks related to the same in-app Browser / Chromium path:

Two Codex main-process crashes occurred in the same desktop thread, at 2026-06-10 10:21:56 and 10:31:54 local time.
Both main-process crash reports show EXC_BREAKPOINT / SIGTRAP with faulting thread CrBrowserMain.
Each main-process crash had a paired Codex (Renderer) crash report in the same second showing SIGABRT.
The triggering browser backend was the in-app browser (agent.browsers.get("iab")), not the external Chrome extension or a normal Chrome profile.

The two observed trigger paths were:

agent.browsers.get("iab"), set viewport to 390x844, open a new in-app browser tab to a public documentation page, wait for domcontentloaded, then call tab.playwright.domSnapshot().
Set up the browser runtime manually, agent.browsers.get("iab"), set viewport to 390x844, open a local preview page, click a UI button, run page.evaluate() to read layout metrics, then reset the viewport and close the tab.

I am intentionally not pasting local project paths, thread IDs, hostnames, or raw crash logs publicly. The useful matching details from the local .ips reports are the app version, EXC_BREAKPOINT / SIGTRAP, CrBrowserMain, and the paired renderer SIGABRT.

Gabbz15 · 2 months ago

I am seeing a very similar crash on Codex Desktop.

Environment:

Codex Desktop: 26.608.12217
macOS: 26.5.1 (25F80)
Machine: Apple Silicon, Mac15,9
Codex/Chromium framework: 149.0.7827.54

Observed behavior:

Codex crashes when interacting with the in-app browser / opening localhost links from Codex.
I also saw a related crash pattern in Chrome Stable 149.0.7827.103 on the same machine when pressing Enter in the address bar or clicking the Back button.
In Codex, the crash happens in the main process with EXC_BREAKPOINT / SIGTRAP.
Crashed thread: CrBrowserMain.
The renderer process also aborts shortly after.

Relevant crash report details:

Main Codex crash: EXC_BREAKPOINT (SIGTRAP), CrBrowserMain
Renderer crash: EXC_CRASH / SIGABRT
Codex version: 26.608.12217
macOS version: 26.5.1

This does not appear to be caused by project code. It looks related to the Codex in-app browser / Chromium UI runtime on macOS 26.x.