[ruby-core:56598] [ruby-trunk - Bug #8483] SEGV under high concurrency

Issue #8483 has been updated by diego.plentz (Diego Plentz).


We found the problem, was a recursive call that was generating the problem. I think it's really a bug that it segfaults in a recursive call when we had less memory, but I really can't reproduce the error in a more restrict test case, so I think we can close this. Thanks anyway
----------------------------------------
Bug #8483: SEGV under high concurrency
https://bugs.ruby-lang.org/issues/8483#change-41134

Author: diego.plentz (Diego Plentz)
Status: Feedback
Priority: Normal
Assignee: 
Category: core
Target version: 
ruby -v: ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


Follow a few segfaults from /var/log/messages https://gist.github.com/plentz/5701752

I'm using sidekiq at my production servers and the ruby process dies with a segfault constantly(it's dying constantly since the last 2 weeks). I'm using concurrency of 50 with sidekiq, which causes a lot of threads to run.

I'm using ruby-2.0.0p195, but the problem happens with ruby-1.9.3-p392, ruby-1.9.3-p429 and ruby-2.0.0p0 as well. I already rollbacked all our gems, which probably means that the problem is really something with our ruby code causing the problem and not some gem that we use.

Here's what I managed to get using gdb

https://gist.github.com/plentz/5630854
https://gist.github.com/plentz/5632256

I can't find which line of the code is triggering the problem, since right after the segfault, I can't call (gdb) call rb_backtrace() to find the ruby stacktrace(or just don't know how).

If someone give me some directions, I can get more info, since the problem happens very often in our environment.


-- 
http://bugs.ruby-lang.org/