Issue #7350 has been reported by ggiesemann (Geoffrey Giesemann). ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350 Author: ggiesemann (Geoffrey Giesemann) Status: Open Priority: Normal Assignee: Category: 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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.
on 2012-11-14 06:08
on 2012-11-14 06:34
Issue #7350 has been updated by usa (Usaku NAKAMURA). 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? ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-32894 Author: ggiesemann (Geoffrey Giesemann) Status: Open Priority: Normal Assignee: Category: 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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.
on 2012-11-20 00:37
Issue #7350 has been updated by ggiesemann (Geoffrey Giesemann). 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 http://libxml.rubyforge.org/rdoc/) 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. ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-33137 Author: ggiesemann (Geoffrey Giesemann) Status: Open Priority: Normal Assignee: Category: 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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-trunk - Bug #7350][Feedback] Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux
on 2012-11-24 10:12
Issue #7350 has been updated by mame (Yusuke Endoh). 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 <mame@tsg.ne.jp> ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-33804 Author: ggiesemann (Geoffrey Giesemann) Status: Feedback Priority: Normal Assignee: Category: Target version: 2.0.0 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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.
on 2013-02-17 05:59
Issue #7350 has been updated by ko1 (Koichi Sasada). Assignee set to mame (Yusuke Endoh) ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-36364 Author: ggiesemann (Geoffrey Giesemann) Status: Feedback Priority: Normal Assignee: mame (Yusuke Endoh) Category: Target version: 2.0.0 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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-trunk - Bug #7350][Rejected] Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux
on 2013-02-17 06:50
Issue #7350 has been updated by mame (Yusuke Endoh). Status changed from Feedback to Rejected Marking as rejected due to no response from OP. -- Yusuke Endoh <mame@tsg.ne.jp> ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-36393 Author: ggiesemann (Geoffrey Giesemann) Status: Rejected Priority: Normal Assignee: mame (Yusuke Endoh) Category: Target version: 2.0.0 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 https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 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.
Enable email notification
Enable multi-page viewPlease log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.