Project

General

Profile

Actions

Backport #5661

closed

Segfault in Random.rand with Spork gem

Added by Odaeus (Andrew France) over 12 years ago. Updated over 11 years ago.

Status:
Closed
[ruby-core:41209]

Description

When running my Rails 3.1 RSpec suite with the Spork gem I get a Segmentation Fault caused by the Random.rand method.

The full debug output is attached. Sorry I have not been able to isolate the code to a minimum test case. Suggestions on reproducing with less code would be welcome.

The offending code is in a Factory Girl factory definition:

trait :with_messages do
after_create do |mt|
user = FactoryGirl.create(:user) # To prevent creating 1 user per message
FactoryGirl.create_list(:message, 1 + Random.rand(4), thread: mt, created_by: user)
end
end

Spork is loaded with: bundle exec spork rspec
The fault occurs when the test run is executed with: bundle exec rspec spec
It works fine when not running in the Spork process.


Files

rspec.saved (263 KB) rspec.saved Segfault output Odaeus (Andrew France), 11/23/2011 03:32 AM
0001-random.c-random_s_rand-avoid-segfault-after-fork-rub.patch (1.89 KB) 0001-random.c-random_s_rand-avoid-segfault-after-fork-rub.patch normalperson (Eric Wong), 11/23/2011 05:45 AM

Related issues 1 (0 open1 closed)

Has duplicate Backport193 - Backport #7159: SIGSEGV when calling Random#rand after forkingClosedusa (Usaku NAKAMURA)10/15/2012Actions

Updated by Odaeus (Andrew France) over 12 years ago

Sigh, sorry I appear to have used a bad formatter code and can't edit the ticket.

Updated by normalperson (Eric Wong) over 12 years ago

Attached patch should fix it (test cases included).
git users: git pull git://bogomips.org/ruby.git random-fork

Until the next Ruby release, Spork can workaround this by using
"rand(4)" instead of "Random.rand(4)"

Updated by ko1 (Koichi Sasada) about 12 years ago

  • Category set to core
  • Assignee set to nahi (Hiroshi Nakamura)
Actions #5

Updated by nobu (Nobuyoshi Nakada) about 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r34977.
Andrew, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


  • random.c (random_s_rand): ensure default PRNG is re-initialized
    after fork. patched by Eric Wong. [ruby-core:41209][Bug #5661]
Actions #6

Updated by nobu (Nobuyoshi Nakada) over 11 years ago

  • Tracker changed from Bug to Backport
  • Project changed from Ruby master to Backport193
  • Category deleted (core)
  • Status changed from Closed to Assigned
  • Assignee changed from nahi (Hiroshi Nakamura) to usa (Usaku NAKAMURA)
Actions #7

Updated by usa (Usaku NAKAMURA) over 11 years ago

  • Status changed from Assigned to Closed

This issue was solved with changeset r37208.
Andrew, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


merge revision(s) 34977: [Backport #5661]

* random.c (random_s_rand): ensure default PRNG is re-initialized
  after fork.  patched by Eric Wong.  [ruby-core:41209][Bug #5661]
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0