Bug #7350

Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux]

Added by Geoffrey Giesemann over 4 years ago. Updated about 4 years ago.

Target version:
ruby -v:
ruby 1.9.3p328 (2012-11-13) [x86_64-linux]


I'm experiencing sporadic segmentation faults in a ruby daemon running with:

ruby 1.9.3p328 (2012-11-13) [x86_64-linux]

This is actually the 1.9.3p327 ruby patched with as the issue looked similar to the one I was experiencing.

The daemon in question sits in a loop pulling messages out of an ActiveMQ server using the stomp gem; DOM parsing a file locally using libxml-ruby; then stuffing another message back on to the server using the same stomp client. I haven't been able to isolate the problem into a smaller block; but I can reproduce it in ~15 minutes on an AWS test server.

I've included two examples of crash output, I have several more from 1.9.3p286.

Happy to try patches or anything further to help debug/diagnose the issue.

ruby-1.9.3p328.crash1.log View (27.6 KB) Geoffrey Giesemann, 11/14/2012 02:08 PM

ruby-1.9.3p328.crash2.log View (27.7 KB) Geoffrey Giesemann, 11/14/2012 02:08 PM


#1 [ruby-core:49336] Updated by Usaku NAKAMURA over 4 years ago

Can you check with trunk?

Yes, it may be difficult, I know.

It seems that crash1.log suggests the cause is in libxml-ruby gem, maybe GC bug.
crash2.log suggests ... ..... a string passed to Pathname is broken.

Does anyone have any idea?

#2 [ruby-core:49623] Updated by Geoffrey Giesemann over 4 years ago

Argh, my bad - I think it's a problem with how we were using libxml-ruby rather thank a ruby bug.

We had an area of code where we weren't correctly importing nodes into documents (see "Memory Management" in which looks like it caused bizarro heap corruption :S

For some reason this is much easier to replicate when you have a deeper call stack - like if you're inside a stomp gem handling a message frame - than it is with a vanilla code sample.

I have a reasonably small code sample to reproduce this, but you'll need a STOMP server to make it work.

#3 [ruby-core:50030] Updated by Yusuke Endoh over 4 years ago

  • Status changed from Open to Feedback
  • Target version set to 2.0.0

Could you show the small code sample?
I'm very happy if you kindly show the process to setup STOMP server :-)
We can make no progress without it.

Yusuke Endoh

#4 [ruby-core:52321] Updated by Koichi Sasada about 4 years ago

  • Assignee set to Yusuke Endoh

#5 [ruby-core:52348] Updated by Yusuke Endoh about 4 years ago

  • Status changed from Feedback to Rejected

Marking as rejected due to no response from OP.

Yusuke Endoh

Also available in: Atom PDF