Codex Desktop shows elevated renderer/GPU-process activity on macOS

Open 💬 1 comment Opened Jun 14, 2026 by ninjiez

Summary

Codex Desktop can show elevated renderer/GPU-process activity and sustained GPU residency on macOS. Filing separately from the syspolicyd/trustd issue because this appears as a distinct high-energy/GPU symptom.

Environment

  • macOS: 26.5.1 (25F80)
  • Architecture: arm64
  • Codex Desktop: Electron/Chromium framework 149.0.7827.54 observed in process args
  • Power state during sampling: AC attached, internal battery 80%, not charging

Observed behavior

While Codex Desktop was open, local samples showed Codex renderer/GPU-process activity:

  • ps: Codex (Service) --type=gpu-process at 11.4% CPU
  • ps: Codex (Renderer) at 17.7% CPU
  • top: Codex (Renderer) 11.2%, Codex (Service) 6.3%, Codex main process 13.4%
  • powermetrics --samplers tasks: Codex (Renderer) between 206 and 285 CPU ms/s in consecutive samples
  • powermetrics: Codex main process up to 211 CPU ms/s, Codex (Service) up to 85 CPU ms/s
  • powermetrics --samplers gpu_power: GPU HW active residency around 18-20%, GPU power around 293-325 mW, GPU SW requested state P1 at 100%
  • pmset assertions: Codex held a NoIdleSleepAssertion named Electron

Expected behavior

When Codex is not actively rendering a heavy scene or performing browser/computer-use automation, renderer and GPU-process usage should return close to idle and should not keep a high-energy state active.

Notes / attribution caveat

The same sample also showed Chrome audio/video wake locks, so I am not attributing all system GPU residency exclusively to Codex. The Codex-specific processes above were still consistently active enough to show up in top/ps/powermetrics, including the Codex GPU process and renderer. Please let me know what additional diagnostics would best isolate renderer repaint/GPU activity.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗