Bug #8483

SEGV under high concurrency

Added by diego.plentz (Diego Plentz) almost 5 years ago. Updated almost 5 years ago.

Target version:
ruby -v:
ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-linux]


Follow a few segfaults from /var/log/messages

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

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.


#1 [ruby-core:55767] Updated by nagachika (Tomoyuki Chikanaga) almost 5 years ago

Do you use any gem packages contains extension libraries?
Can you run a process in terminal and get backtrace etc..

#2 [ruby-core:56429] Updated by naruse (Yui NARUSE) almost 5 years ago

  • Status changed from Open to Feedback
  • Priority changed from 5 to Normal

Could you provide a reproducible code?

#3 Updated by diego.plentz (Diego Plentz) almost 5 years ago

nagachika (Tomoyuki Chikanaga) Yes, but I really think the problem isn't related to that.
naruse (Yui NARUSE) Not yet. I'm still trying to reproduce the problem.

Right now, I've found some more info. After a increase in server memory(we added 4GBs of ram), we stopped seeing the segfaults and started to see "stack level too deep". All errors we have are listed bellow(curiously, they all point to lines with "raise"s):

#4 [ruby-core:56598] Updated by diego.plentz (Diego Plentz) almost 5 years ago

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

Also available in: Atom PDF