Multiprocessing exitcode=None after join
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
I sometimes observe exitcode=None after joining a process.
import multiprocessing as mp
import sys
import threading
sys.setswitchinterval(1e-6)
ctx = mp.get_context("fork")
failures = []
def lifecycle(n_iters=100, n_procs=4):
for _ in range(n_iters):
ps = [ctx.Process(target=int, daemon=True) for _ in range(n_procs)]
for p in ps:
p.start()
for p in ps:
p.join()
if p.exitcode is None:
failures.append(p.pid)
ts = [threading.Thread(target=lifecycle) for _ in range(2)]
for t in ts:
t.start()
for t in ts:
t.join()
print(f"{len(failures)}/{2*100*4} had exitcode=None after join()")
CPython versions tested on:
3.13
Operating systems tested on:
Linux
Linked PRs
- gh-150360
Contributor guide
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 running the supplied Linux Python 3.13 reproducer, focusing on multiprocessing with the fork context and concurrent lifecycle calls. Review linked PR gh-150360 and verify that joining a process consistently yields a non-None exitcode without regressing the threaded case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100