Possible macOS resource-pressure issue when running Codex CLI inside zellij/Ghostty during long-lived sessions

Possible macOS resource-pressure issue when Codex CLI is used inside zellij/Ghostty during long-lived sessions.

Context:

• macOS 26.3.2 on Apple Silicon (M3 Max, 36 GB RAM)
• zellij 0.44.1
• Ghostty 1.3.1
• long-running session with heavy streamed output and background panes

Observed from diagnostics:

• multiple codex-aarch64-apple-darwin processes with nontrivial memory footprint
• APFS ENOSPC log lines named codex-aarch64-apple-darwin seconds before:
• low swap: failed to create swapfile
• memorystatus: System is unhealthy
• watchdog panic

I am not claiming Codex was the sole root cause, because the machine had broader resource pressure. But given #9345 and existing zellij compatibility reports, I'm wondering whether heavy TUI streaming / large file operations inside zellij can retain memory or amplify scrollback / disk churn on macOS.

Happy to attach redacted logs if useful.