Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0

• Status: Closed
• Priority: Normal
• Assignee: -

[headius (Charles Nutter)]

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.

[normalperson (Eric Wong)]

This is fixed in Ruby 2.0.0 p451, seems related to
https://bugs.ruby-lang.org/issues/9178

[usa (Usaku NAKAMURA)]

• Status changed from Open to Closed

see r44150.

[hansdegraaff (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.

[usa (Usaku NAKAMURA)]

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

[hansdegraaff (Hans de Graaff)]

• File threadsafe-ruby21.txt threadsafe-ruby21.txt added

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).

[hansdegraaff (Hans de Graaff)]

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