Project

General

Profile

Actions

Bug #18444

open

Trapped TSTP causes a locking deadlock in 3.0.3 onward

Added by why-el (Mohamed Wael Khobalatte) almost 3 years ago. Updated over 2 years ago.

Status:
Open
Assignee:
-
Target version:
-
[ruby-core:106867]

Description

A curious case:

ruby -e 'Signal.trap("TSTP") { puts "Received a terminal stop signal, but i will sleep instead."; sleep 10 }; loop {puts 1}'

this fails with deadlock; recursive locking (ThreadError) when I send the SIGTSTP via my terminal. This is on Mac OS Monterey (M1). It only happens in 3.0.3 and onward (I tried 3.1.0-preview1 as well, fails there too), when I try 3.0.2, the signal is handled properly.

Actions

Also available in: Atom PDF

Like0
Like0Like0