https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112011-09-24T10:23:07ZRuby Issue Tracking SystemBackport193 - Backport #5359: rails 3.1, nokogiri-1.5.0 - Segmentation faulthttps://bugs.ruby-lang.org/issues/5359?journal_id=209622011-09-24T10:23:07Znormalperson (Eric Wong)normalperson@yhbt.net
<ul></ul><p>Slava Mikerin <a href="mailto:slava@slavix.com" class="email">slava@slavix.com</a> wrote:</p>
<blockquote>
<p>Backport <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: rails 3.1, nokogiri-1.5.0 - Segmentation fault (Closed)" href="https://bugs.ruby-lang.org/issues/5359">#5359</a>: rails 3.1, nokogiri-1.5.0 - Segmentation fault<br>
<a href="http://redmine.ruby-lang.org/issues/5359" class="external">http://redmine.ruby-lang.org/issues/5359</a></p>
</blockquote>
<p>I don't see anything that indicates this should be a backport.</p>
<p>Can you give us more information (code/commands used) on how to<br>
reproduce this issue?</p>
<blockquote>
<p>[2011-09-23 17:01:41] INFO WEBrick::HTTPServer#start: pid=25568 port=3000<br>
/home/slava/.rvm/gems/ruby-1.9.3-preview1/gems/nokogiri-1.5.0/lib/nokogiri/xml/node.rb:522: [BUG] Segmentation fault<br>
ruby 1.9.3dev (2011-07-31 revision 32789) [i686-linux]</p>
</blockquote> Backport193 - Backport #5359: rails 3.1, nokogiri-1.5.0 - Segmentation faulthttps://bugs.ruby-lang.org/issues/5359?journal_id=210152011-09-27T03:23:08Zender672 (Timothy Elliott)tle@holymonkey.com
<ul></ul><p>On Fri, Sep 23, 2011 at 5:12 PM, Slava Mikerin <a href="mailto:slava@slavix.com" class="email">slava@slavix.com</a> wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: rails 3.1, nokogiri-1.5.0 - Segmentation fault (Closed)" href="https://bugs.ruby-lang.org/issues/5359">#5359</a> has been reported by Slava Mikerin.</p>
<hr>
<p>Backport <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: rails 3.1, nokogiri-1.5.0 - Segmentation fault (Closed)" href="https://bugs.ruby-lang.org/issues/5359">#5359</a>: rails 3.1, nokogiri-1.5.0 - Segmentation fault<br>
<a href="http://redmine.ruby-lang.org/issues/5359" class="external">http://redmine.ruby-lang.org/issues/5359</a></p>
</blockquote>
<p>Hi Slava,</p>
<p>This looks like it might be a Nokogiri bug. I've fixed a few segfaults<br>
in Nokogiri lately, and I would like to fix this one too. You can see<br>
my Nokogiri pull requests here --<br>
<a href="https://github.com/tenderlove/nokogiri/pulls" class="external">https://github.com/tenderlove/nokogiri/pulls</a> .</p>
<p>However, I don't know how to reproduce your issue. It looks like you<br>
are running a Rails project to trigger the bug.</p>
<p>Can you zip up the project and email it to me? If it is not an<br>
opensource project and you have concerns about sending it, can you<br>
reproduce the bug in a new project with just a few files copied over?</p>
<p>Cheers,<br>
Tim</p> Backport193 - Backport #5359: rails 3.1, nokogiri-1.5.0 - Segmentation faulthttps://bugs.ruby-lang.org/issues/5359?journal_id=212432011-10-08T20:38:23Zkosaki (Motohiro KOSAKI)kosaki.motohiro@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>It seems 3rd party issue.</p>