[ruby-core:90312] [Ruby trunk Bug#15383] Reproducible crash: crash.sh:6: [BUG] unexpected THREAD_KILLED

[mbj@schirp-dso.com]

Issue #15383 has been reported by mbjs (Markus Schirp).

----------------------------------------
Bug #15383: Reproducible crash: crash.sh:6: [BUG] unexpected THREAD_KILLED
https://bugs.ruby-lang.org/issues/15383

* Author: mbjs (Markus Schirp)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Hi,

I'm reporting a reliable crash of the ruby interpreter on contested mutexeses that are accessed in child processes.

I currently think that this happens as the child processes main thread, may be waiting for a parent process sibling thread that was holding the mutex at the time of the fork. After the fork is done, all sibling threads are dead, and the mutex detects the attempt to wait for a dead thread, bailing out.

This is simular, but not identical to the case here: https://bugs.ruby-lang.org/issues/14578

Here is a gist with some more test results on various platforms: https://gist.github.com/mbj/e6795ee5e0583c5541ee250e9942279a

I'm fine to get my hands dirty, but would need some pointers if my above conclusion points to the right direction.

Best,

Markus

---Files--------------------------------
output.txt (21.3 KB)
crash.rb (200 Bytes)


-- 
https://bugs.ruby-lang.org/