`multiprocessing.Process.is_alive()` can incorrectly return True after `join()`
@gpshead 已經在處理了。
開始於 2026年1月11日。
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- PR 合併指標
- PR 指標待擷取
描述
Bug report
Bug description:
This came up in https://github.com/python/cpython/pull/130849#discussion_r1980137089
The problem is that popen_fork.Popen (and popen_spawn.Popen and popen_forkserver.Popen) are not thread-safe:
The first successful call to os.waitpid() may reap the pid so that subsequent calls raise an OSError. I've only seen this on macOS (not Linux). We may not yet however have set self.returncode -- that happens a few statements later, so poll() can return None if:
- The process has finished
- Another thread called poll(), but hasn't yet set
self.returncode
And then is_alive() can return True:
Note that some classes like concurrent.futures.ProcessPoolExecutor use threads internally, so the user may not even know that threads are involved.
Repro:
repro.py
import os
import multiprocessing as mp
import threading
import time
import sys
original_excepthook = threading.excepthook
def on_except(args):
original_excepthook(args)
os._exit(1)
threading.excepthook = on_except
def p1():
pass
def thread1(p):
while p.is_alive():
time.sleep(0.00001)
pass
def test():
for i in range(1000):
print(i)
p = mp.Process(target=p1)
p.start()
t = threading.Thread(target=thread1, args=(p,))
t.start()
p.join()
assert not p.is_alive()
t.join()
def main():
threads = [threading.Thread(target=test) for _ in range(10)]
for t in threads:
t.start()
for t in threads:
t.join()
if __name__ == "__main__":
main()
NOTE:
- This is unrelated to free threading
popen_fork.Popen(and subclasses) are distinct fromsubprocess.Popen
CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS
Linked PRs
- gh-131440
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
評估
這個 Issue 還沒有評估資料。