python / python/cpython

Sending many signals to a Python process crashes the interpreter

未關閉
#118,143 9 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

type-bug
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

Bug report

Bug description:

Consider the following simple program (test-breakage.py):

from time import sleep
import os
import signal


class Foreman:
    def __init__(self):
        signal.signal(signal.SIGUSR1, self.handle_sigusr1)
        pid = os.getpid()
        print("Test script created, my pid is %s", pid)
        with open("/tmp/test-breakage.pid", "w") as f:
            f.write(str(pid))

    def handle_sigusr1(self, sig, frame):
        print("handle_sigusr1")

    def run_forever(self):
        sleep(3600)


Foreman().run_forever()

Now, a tool to send "a lot" of signal to it:

import os
import sys
import signal


pid = int(sys.argv[1])
iterations = int(sys.argv[2])

for i in range(iterations):
    os.kill(pid, signal.SIGUSR1)

Or, if you want the signals to be sent more quickly, implemented in c:

#include <stdlib.h>
#include <signal.h>


int main(int argc, char*argv[]) {
    long pid, iterations;
    if (argc > 2) {
        pid = strtol(argv[1], NULL, 0);
        iterations = strtol(argv[2], NULL, 0);

        for (int i = 0; i < iterations; i++) {
            kill(pid, SIGUSR1);
        }
   }
   return 0;
}

Running these scripts with "sufficiently high" numbers results in various crashes in test-breakage

  • Exit with "User defined signal 1" (shouldn't happen, we've defined a handler)
  • RuntimeError without any further information
  • Exit without any printed string
  • RuntimeError: reentrant call inside <_io.BufferedWriter name=''>

(In all cases, after repeating "handle_sigusr1" a number of times first)

tested on Linux w. Python 3.10

CPython versions tested on:

3.10

Operating systems tested on:

Linux

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

Start by reproducing the failure with the test-breakage.py signal handler and the Python or C signal-sending scripts on Linux. Compare the reported outcomes under sustained SIGUSR1 delivery; done means the interpreter remains stable and the registered handler continues to behave correctly without the listed crashes or unintended termination.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
python
領域
operating-systems
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
42/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。