Segmentation fault in relation.rb:241

Created by: NikolayMurha

Hello!

After update gtilab in some pages displayed error (502 Bad Gateway)

In unicorn.stderr.log i see error:

ruby 1.9.3p362 (2012-12-25 revision 38607) [i686-linux] /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.9/lib/active_record/relation.rb:241: [BUG] Segmentation fault

Thanx.

Created by: AlexDenisov

Have the same issue. It seems that problem is in Ruby interpreter. Try another version (1.9.3p327 works for me).

By Administrator on 2012-12-29T15:42:38 (imported from GitLab)

Created by: NikolayMurha

1.9.3p327 - worked.

By Administrator on 2012-12-29T15:50:18 (imported from GitLab)

Created by: repsejnworb

Thank you for the info! I've been struggling forever trying to fix my gitlab-vagrant setup, and this was the last piece.

By Administrator on 2012-12-30T14:12:42 (imported from GitLab)

Created by: nbigaouette

I just upgraded to ruby 1.9.3_p362-1 on ArchLinux and have a similar crash:

/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.9/lib/active_record/relation.rb:241: [BUG] Segmentation fault
ruby 1.9.3p362 (2012-12-25 revision 38607) [x86_64-linux]

Downgrading to 1.9.3_p327-1 made gitlab work.

By Administrator on 2013-01-04T17:45:20 (imported from GitLab)

Created by: taras-yorku

Got the same crash with 1.9.3 p362. Works with p327.

Downgrade is the answer here, until they fix whatever the issue is.

By Administrator on 2013-01-10T17:27:33 (imported from GitLab)

Created by: dukejones

p374 should fix this. http://www.ruby-lang.org/en/news/2013/01/17/ruby-1-9-3-p374-is-released/

By Administrator on 2013-01-22T21:53:45 (imported from GitLab)