From: "why-el (Mohamed Wael Khobalatte)" Date: 2021-12-28T16:01:45+00:00 Subject: [ruby-core:106867] [Ruby master Bug#18444] Trapped TSTP causes a locking deadlock in 3.0.3 onward Issue #18444 has been reported by why-el (Mohamed Wael Khobalatte). ---------------------------------------- Bug #18444: Trapped TSTP causes a locking deadlock in 3.0.3 onward https://bugs.ruby-lang.org/issues/18444 * Author: why-el (Mohamed Wael Khobalatte) * Status: Open * Priority: Normal * ruby -v: 3.0.3 * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- 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. -- https://bugs.ruby-lang.org/ Unsubscribe: