Project

General

Profile

Backport #9649

Segfault running thread_safe torture tests under Ruby 2.0

Added by Charles Nutter about 2 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
[ruby-core:61553]

Description

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.

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

History

#1 [ruby-core:61566] Updated by Eric Wong about 2 years ago

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

#2 [ruby-core:62236] Updated by Usaku NAKAMURA about 2 years ago

  • Status changed from Open to Closed

see r44150.

#3 [ruby-core:69930] Updated by Hans de Graaff 11 months 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 https://github.com/ruby-concurrency/thread_safe/issues/21 for a new bug report on this including backtrace.

#4 [ruby-core:69933] Updated by Usaku NAKAMURA 11 months ago

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

#5 [ruby-core:70134] Updated by Hans de Graaff 10 months 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).

#6 [ruby-core:70136] Updated by Hans de Graaff 10 months 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