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

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

[mbj]

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/

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

[Eric Wong]

> https://bugs.ruby-lang.org/issues/15383

Thanks, it affects trunk; just more difficult to reproduce
because of thread cache.

I'm a moron for not noticing this when I fixed other bugs :<

r66230 should fix it in trunk and should be backported
(but r66229 is independently broken and I just reverted it for now)

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

[Eric Wong]

> > https://bugs.ruby-lang.org/issues/15383

> r66230 should fix it in trunk and should be backported

No, actually.  r66230 hides an existing problem in the fix
for https://bugs.ruby-lang.org/issues/14578
...
Still working on this and my head hurts :<

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

[mbj]

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


Thanks for the quick fix. Also for marking the fix to be backported.

Just curious, is there an associated CI build for these changes?

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

* Author: mbjs (Markus Schirp)
* Status: Closed
* 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: REQUIRED
----------------------------------------
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/

[ruby-core:90328] Re: [Ruby trunk Bug#15383] Reproducible crash: crash.rb:6: [BUG] unexpected THREAD_KILLED

[Eric Wong]

mbj@schirp-dso.com wrote:
> Just curious, is there an associated CI build for these changes?

I check https://rubyci.org/ and http://ci.rvm.jp/ (and get
automated mails from the latter).

There's also TravisCI; but I don't use JavaScript; so I rely
on others giving me URLs to the raw logs.