Backport #9649


Segfault running thread_safe torture tests under Ruby 2.0

Added by headius (Charles Nutter) over 8 years ago. Updated about 7 years ago.



We received the following report on the thread_safe project:

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.


threadsafe-ruby21.txt (32.8 KB) threadsafe-ruby21.txt hansdegraaff (Hans de Graaff), 07/27/2015 07:34 PM

Updated by normalperson (Eric Wong) over 8 years ago

This is fixed in Ruby 2.0.0 p451, seems related to

Updated by usa (Usaku NAKAMURA) over 8 years ago

  • Status changed from Open to Closed

see r44150.

Updated by hansdegraaff (Hans de Graaff) about 7 years ago

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 for a new bug report on this including backtrace.

Updated by usa (Usaku NAKAMURA) about 7 years ago

The normal maintenance phase of ruby 2.0.0 is already ended.
Try ruby 2.1 or 2.2.

Updated by hansdegraaff (Hans de Graaff) about 7 years ago

I can also reproduce this with ruby 2.1 (note that it may take a couple of test runs of the threadsafe test suite to trigger this).

Updated by hansdegraaff (Hans de Graaff) about 7 years ago

So far I have not been able to reproduce this with ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]


Also available in: Atom PDF