Forum: Ruby-core [Backport 200 - Backport #8874][Open] libruby.so.2.0 variable.c segmentation faults in production wi

0c8fab048254a5ef957eb1a19e6bbcbe?d=identicon&s=25 odog (Owen Tran) (Guest)
on 2013-09-07 19:14
(Received via mailing list)
Issue #8874 has been reported by odog (Owen Tran).

----------------------------------------
Backport #8874: libruby.so.2.0 variable.c segmentation faults in
production with rails (ruby-2.0.0-p247)
https://bugs.ruby-lang.org/issues/8874

Author: odog (Owen Tran)
Status: Open
Priority: High
Assignee:
Category:
Target version:


Recently upgraded rails application from ruby-2.0.0-p195 to
ruby-2.0.0-p247 and seeing frequent segmentation faults now when rails
action-4.0.0 calls the inspect method which loops through all the
variables.

/var/www/pointshound/shared/bundle/ruby/2.0.0/gems/actionpack-4.0.0/lib/action_dispatch/request/session.rb:132:
[BUG] Segmentation fault
ruby 2.0.0p247 (2013-06-27 revision 41674) [i686-linux]

-- C level backtrace information
-------------------------------------------
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1aefb0)
[0xb76effb0] vm_dump.c:647
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x5bf4d)
[0xb759cf4d] error.c:283
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_bug+0x40)
[0xb759dc90] error.c:302
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x12f51d)
[0xb767051d] signal.c:672
[0xf57fe40c]
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_ivar_count+0xe8)
[0xb76b9cd8] variable.c:1303
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0xbef06)
[0xb75fff06] object.c:498
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1954fe)
[0xb76d64fe] vm_insnhelper.c:1331
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1a3670)
[0xb76e4670] vm_eval.c:117
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_funcall+0xc7)
[0xb76e6057] vm_eval.c:49
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_inspect+0x40)
[0xb7600df0] object.c:404

(full crash.log attached)

Not quite sure how to reproduce, other than letting it run in production
until it hits this segfault. Right now, restarting application whenever
this happens but impacts stability.
Eabad423977cfc6873b8f5df62b848a6?d=identicon&s=25 hsbt (Hiroshi SHIBATA) (Guest)
on 2013-11-27 04:13
(Received via mailing list)
Issue #8874 has been updated by hsbt (Hiroshi SHIBATA).

Status changed from Open to Feedback
ruby -v set to 2.0.0-p247

Please feedback to run your code with ruby-trunk.
----------------------------------------
Bug #8874: libruby.so.2.0 variable.c segmentation faults in production
with rails (ruby-2.0.0-p247)
https://bugs.ruby-lang.org/issues/8874#change-43190

Author: odog (Owen Tran)
Status: Feedback
Priority: High
Assignee:
Category:
Target version:
ruby -v: 2.0.0-p247
Backport:


Recently upgraded rails application from ruby-2.0.0-p195 to
ruby-2.0.0-p247 and seeing frequent segmentation faults now when rails
action-4.0.0 calls the inspect method which loops through all the
variables.

/var/www/pointshound/shared/bundle/ruby/2.0.0/gems/actionpack-4.0.0/lib/action_dispatch/request/session.rb:132:
[BUG] Segmentation fault
ruby 2.0.0p247 (2013-06-27 revision 41674) [i686-linux]

-- C level backtrace information
-------------------------------------------
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1aefb0)
[0xb76effb0] vm_dump.c:647
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x5bf4d)
[0xb759cf4d] error.c:283
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_bug+0x40)
[0xb759dc90] error.c:302
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x12f51d)
[0xb767051d] signal.c:672
[0xf57fe40c]
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_ivar_count+0xe8)
[0xb76b9cd8] variable.c:1303
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0xbef06)
[0xb75fff06] object.c:498
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1954fe)
[0xb76d64fe] vm_insnhelper.c:1331
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(+0x1a3670)
[0xb76e4670] vm_eval.c:117
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_funcall+0xc7)
[0xb76e6057] vm_eval.c:49
/home/pointshound/.rvm/rubies/ruby-2.0.0-p247/lib/libruby.so.2.0(rb_inspect+0x40)
[0xb7600df0] object.c:404

(full crash.log attached)

Not quite sure how to reproduce, other than letting it run in production
until it hits this segfault. Right now, restarting application whenever
this happens but impacts stability.
This topic is locked and can not be replied to.