Issue #9649 has been updated by Hans de Graaff.


I can still reproduce this issue with ruby 2.0.0p645 (2015-04-13 revision 50299) [x86_64-linux] and thread_safe 0.3.5. The error is not consistent, so it may take a couple of runs to actually hit the problem.

See https://github.com/ruby-concurrency/thread_safe/issues/21 for a new bug report on this including backtrace.

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53353

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



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