Codex desktop crashes with SIGTRAP after accumulating NetworkConfigWatcher threads

Summary

The Codex desktop app crashed on macOS after running for approximately 21.5 hours. The macOS crash report shows 45 NetworkConfigWatcher threads at the time of the crash, which may indicate that network watcher threads are accumulating during the app lifetime.

Environment

• Codex desktop: 26.707.72221 (build 5307)
• Codex Framework: 150.0.7871.115
• macOS: 26.5.2 (25F84)
• Hardware: MacBook Pro Mac16,8, Apple M4 Pro, 48 GB RAM
• Incident ID: 33693781-CEED-440F-8218-92B4F49CB169
• External display: Dell U2722DE
• Dock: StarTech TB3DK2DHV

Crash details

• Exception: EXC_BREAKPOINT (SIGTRAP)
• Termination: Namespace SIGNAL, Code 5, Trace/BPT trap: 5
• Triggered thread: CrBrowserMain on com.apple.main-thread
• Process role: Background
• Launch time: 2026-07-13 15:57:27 +0100
• Crash time: 2026-07-14 13:34:09 +0100
• The report shows 45 NetworkConfigWatcher threads.
• The External Modification Summary reports no external process modifications.

Steps to reproduce

No reliable reproduction steps yet. The crash occurred after a long-running app session. The machine had Wi-Fi and Thunderbolt Ethernet hardware present and had gone through a sleep/wake cycle. Network changes, VPN changes, or dock reconnection may be relevant, but this is not confirmed.

Expected behavior

Codex should remain stable across long-running sessions, sleep/wake cycles, and network-interface changes without accumulating watcher threads.

Additional context

The symbols in the stripped framework appear imprecise, so entries such as ares_llist_replace_destructor and rust_png may be nearest-symbol matches rather than the actual failing functions. I can provide the complete macOS crash report privately if needed; it includes local machine details and has not been attached publicly.