openai / openai/codex-plugin-cc
Test suite leaks broker processes — 158 orphans found
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 33.3k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Running the codex plugin test suite spawns app-server-broker.mjs processes for each test workspace (/tmp/codex-plugin-test-*), but these processes are never cleaned up after tests complete.
Found 158 stale broker processes on a development machine, each holding a /tmp/cxc-* socket directory. All were from old test runs (dated Apr 3–6), pointing at temp dirs that may or may not still exist.
Evidence
$ ps aux | grep 'app-server-broker.mjs' | grep -v grep | wc -l
167
$ ps aux | grep 'app-server-broker.mjs' | grep -v grep | grep -oP '(?<=--cwd )\S+' | sort | uniq -c | sort -rn | head -5
1 /tmp/codex-plugin-test-zxrQqX
1 /tmp/codex-plugin-test-znwec8
... (158 test dirs total)
$ ls -d /tmp/cxc-* | wc -l
168
Expected behavior
Test teardown should kill broker processes it spawned (or the broker should self-terminate when its cwd disappears / after idle timeout).
Impact
- Resource leak: 167 node processes × ~35MB RSS = ~5.8GB wasted
- Socket dir accumulation in /tmp
- May contribute to Codex review failures when the system is under resource pressure
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the test-suite teardown that launches app-server-broker.mjs for /tmp/codex-plugin-test-* workspaces. Reproduce the suite and inspect whether spawned brokers and /tmp/cxc-* socket directories are tracked. Done means test-spawned brokers no longer remain after teardown and the resource accumulation described here is prevented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100