This project is archived and is in readonly mode.

#4488 ✓wontfix
Steve Alex

Segmentation fault ruby 1.9.1

Reported by Steve Alex | April 27th, 2010 @ 06:44 PM

I've been experimenting with Rails 3.0.0.beta3. I first started with a few simple models and got a handle of some of changes. I could not get the rails upgrade plugin to work so I started from scratch and generated scaffolds on a nested model (assessments, questions, answers) and things seemed to be working fine after I figured out how to get my routing to work with the lack of :shallow => true.

I was experimenting with new activeRecord queries in the index action for questions

@questions = Assessment.find(params[:assessment_id]).questions

and started to get a segmentation fault. I discovered that I forgot to put my relationships in the models. Putting them in still give me the segmentation fault. Most of the time, the server just locks up and I have to kill the server processess. I can go into rails console and get my finds to work, but not with WEBrick. Sometimes the server will abort. Enclosed is was what was on the server console the last time I got it to abort.

Can't seem to do anything and not sure what happened. Once I saw a postgres compiler error, but postgres is working find in the dbconsole. The attached dump is the most exhaustive I've seen. It starts off with:

=> Ctrl-C to shutdown server [2010-04-27 11:39:27] INFO WEBrick 1.3.1 [2010-04-27 11:39:27] INFO ruby 1.9.1 (2010-01-10) [i386-darwin10.3.0] [2010-04-27 11:39:27] INFO WEBrick::HTTPServer#start: pid=722 port=3000 /Users/salex/.rvm/gems/ruby-1.9.1-p378/gems/activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:426: [BUG] Segmentation fault ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-darwin10.3.0]

-- control frame ---------- c:0023 p:-849038 s:0135 b:0135 l:000134 d:000134 METHOD /Users/salex/.rvm/gems/ruby-1.9.1-p378/gems/activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:426

Rest of dump attached in file railssegfault.txt

Steve Alex

Comments and changes to this ticket

  • Jeremy Kemper

    Jeremy Kemper April 27th, 2010 @ 07:58 PM

    • State changed from “new” to “wontfix”

    Highly recommend switching to 1.9.2 (ruby trunk). Ruby 1.9.1 has had frustrating segfault issues in several stable releases, whereas 1.9.2 has been more stable overall.

    We can't really fix this in Rails, either :)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href=""></a>

People watching this ticket