{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihyabjxf7vhwtfktu2g333hpsaxxur65qxxhhjyeqqhvho46n5iqa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mkgyjr3mlle2"
  },
  "path": "/t/large-number-of-node-repl-exe-processes/1379837#post_1",
  "publishedAt": "2026-04-27T01:16:19.000Z",
  "site": "https://community.openai.com",
  "textContent": "**Title:** Codex Windows app freezes and creates dozens of `node_repl.exe` processes\n\nI am experiencing repeated freezes in the Codex Windows desktop app.\n\nThe app periodically turns white and becomes “not responding” for roughly **20 seconds** before recovering. During this, Task Manager shows a very large number of `node_repl.exe` processes running at the same time.\n\nThis does not look like normal resource pressure: overall CPU and memory are not extremely high. It looks more like Codex is spawning many child REPL processes and not cleaning them up, or not reusing existing sessions properly.\n\n**Expected:**\nThe app should stay responsive and should not accumulate dozens of `node_repl.exe` child processes.\n\n**Observed:**\n\n  * Codex app freezes / white screen\n\n  * “Not responding” for ~20 seconds\n\n  * Dozens of `node_repl.exe` processes visible in Task Manager\n\n  * Each process is small, but the process count is abnormal\n\n\n\n\n**Suggestion:**\nPlease investigate whether `node_repl.exe` processes are being leaked or left alive after tasks finish. A child-process watchdog, reuse strategy, process cap, or cleanup routine may help. It would also be useful to expose diagnostic logs showing when these processes are spawned and terminated.\nScreenshot attached.",
  "title": "Large number of node_repl.exe processes"
}