›_ Codex Issues
Codex Issues / #5243

a lot of background codex process using 98%-100% cpu

Resolved 💬 8 comments Opened Oct 16, 2025 by jiangying000 Closed Oct 21, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.46.0

What subscription do you have?

plus

Which model were you using?

gpt-5,gpt-5-codex

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

I have closed all the terminal.app / vscode window, and still seeing this

<img width="1822" height="396" alt="Image" src="https://github.com/user-attachments/assets/5c65ce33-e574-41ff-b1a9-d3a7012710b9" />

What steps can reproduce the bug?

open codex, talk with it, close terminal.app / vscode after talk

What is the expected behavior?

No background codex process

Additional information

_No response_

View original on GitHub ↗

8 Comments

github-actions[bot] contributor · 9 months ago

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

  • #4726
  • #4337
  • #3836
  • #4592
  • #3269

Powered by Codex Action

MrMage · 9 months ago

I have the same issue. I'm not sure whether any of the suggested duplicates are relevant.

MrMage · 9 months ago

@tibo-openai this is _not_ a duplicate of #1570. In #5243, there is only a _single_ process hogging 100 % CPU, and that process is codex, not node.

pwnsdx · 9 months ago

My M3 Max chip runs between 70–80°C because of this issue. It’s astonishing that OpenAI continues to dismiss such significant problems, and it’s been weeks without a fix. What are they doing, running the entire model on my Mac or something? Either way, it’s a huge waste of energy and is actually damaging users’ hardware around the world.

!Image

pwnsdx · 8 months ago

Can confirm it's fixed on 0.48.0 @MrMage

MrMage · 8 months ago

Sadly, this still happens for me on 0.50.0.

Here's a sample of the codex process recorded using Activity Monitor:

    2154 Thread_2413553   DispatchQueue_1: com.apple.main-thread  (serial)
    + 2154 start  (in dyld) + 6076  [0x187856b98]
    +   2154 ???  (in codex)  load address 0x1028fc000 + 0x49d1f4  [0x102d991f4]
    +     2154 ???  (in codex)  load address 0x1028fc000 + 0x1c60c4  [0x102ac20c4]
    +       2154 ???  (in codex)  load address 0x1028fc000 + 0x482998  [0x102d7e998]
    +         2154 ???  (in codex)  load address 0x1028fc000 + 0x38c994  [0x102c88994]
    +           2154 ???  (in codex)  load address 0x1028fc000 + 0x487014  [0x102d83014]
    +             2154 ???  (in codex)  load address 0x1028fc000 + 0x46a970  [0x102d66970]
    +               2154 ???  (in codex)  load address 0x1028fc000 + 0x457520  [0x102d53520]
    +                 2154 ???  (in codex)  load address 0x1028fc000 + 0x4692bc  [0x102d652bc]
    +                   2154 ???  (in codex)  load address 0x1028fc000 + 0x1320  [0x1028fd320]
    +                     2154 ???  (in codex)  load address 0x1028fc000 + 0xe027e8  [0x1036fe7e8]
    +                       2154 ???  (in codex)  load address 0x1028fc000 + 0xe03258  [0x1036ff258]
    +                         2134 ???  (in codex)  load address 0x1028fc000 + 0xdfc56c  [0x1036f856c]
    +                         ! 2123 read  (in libsystem_kernel.dylib) + 8,4  [0x187bb67dc,0x187bb67d8]
    +                         ! 5 DYLD-STUB$$read  (in codex) + 4  [0x103d1cb1c]
    +                         ! 5 read  (in libsystem_kernel.dylib) + 28  [0x187bb67f0]
    +                         ! : 4 cerror  (in libsystem_kernel.dylib) + 40  [0x187bb74bc]
    +                         ! : 1 cerror  (in libsystem_kernel.dylib) + 52  [0x187bb74c8]
    +                         ! :   1 cerror_nocancel  (in libsystem_kernel.dylib) + 12  [0x187bb65e4]
    +                         ! 1 cerror  (in libsystem_kernel.dylib) + 68  [0x187bb74d8]
    +                         7 ???  (in codex)  load address 0x1028fc000 + 0xdfc6c4  [0x1036f86c4]
    +                         ! 4 ???  (in codex)  load address 0x1028fc000 + 0x1c5c00  [0x102ac1c00]
    +                         ! 2 ???  (in codex)  load address 0x1028fc000 + 0x1c5d4c  [0x102ac1d4c]
    +                         ! 1 ???  (in codex)  load address 0x1028fc000 + 0x1c5c40  [0x102ac1c40]
    +                         5 ???  (in codex)  load address 0x1028fc000 + 0xdfc6b0  [0x1036f86b0]
    +                         ! 3 DYLD-STUB$$__error  (in codex) + 4  [0x103d1c480]
    +                         ! 2 __error  (in libsystem_kernel.dylib) + 4  [0x187bb6600]
    +                         5 ???  (in codex)  load address 0x1028fc000 + 0xdfc6d8  [0x1036f86d8]
    +                         ! 3 ???  (in codex)  load address 0x1028fc000 + 0x1c5c00  [0x102ac1c00]
    +                         ! 1 ???  (in codex)  load address 0x1028fc000 + 0x1c5c24  [0x102ac1c24]
    +                         ! 1 ???  (in codex)  load address 0x1028fc000 + 0x1c5d4c  [0x102ac1d4c]
    +                         1 ???  (in codex)  load address 0x1028fc000 + 0xdfc6c4  [0x1036f86c4]
    +                         1 ???  (in codex)  load address 0x1028fc000 + 0xdfc6d8  [0x1036f86d8]
    +                         1 read  (in libsystem_kernel.dylib) + 36  [0x187bb67f8]
pwnsdx · 8 months ago

Can confirm it is actually still happening. False alarm, sorry. Looks like OpenAI don't give a shit.
!Image

tokict · 5 months ago

I can replicate it every time by leaving it open on my server after disconnecting ssh session