https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112010-06-29T09:34:00ZRuby Issue Tracking SystemBackport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=120652010-06-29T09:34:00Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>=begin<br>
Hi,</p>
<p>Is this reproducible with ruby_1_9_2 or trunk?</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a><br>
=end</p> Backport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=120732010-06-30T00:32:22Zlukaso (Lukas Oberhuber)lukaso@gmail.com
<ul></ul><p>=begin<br>
I tried to run my application with 1.9.1-head. This did not work, probably because of was running into the GEM_HOME issue which kept the app from using sqlite. I've now tested the application on 1.9.2 preview 3, which appears to be working flawlessly.</p>
<p>On 1.9.1, the crashes were occurring quite frequently but always in slightly different places (I can attach more stack dumps if this would help).</p>
<p>-Lukas Oberhuber<br>
=end</p> Backport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=120742010-06-30T06:51:31Zlukaso (Lukas Oberhuber)lukaso@gmail.com
<ul></ul><p>=begin<br>
Well, I spoke too soon, as 1.9.2 preview 3 has also segfaulted. Here is the partial stack trace (the process froze and had to be kill -9 ed to shut down). Unfortunately I don't have a reliable test case. Maybe memory is being corrupted.</p>
<p>Processing UsersController#create to xml (for 127.0.0.1 at 2010-06-29 19:41:07) [POST]<br>
Parameters: {"user"=>nil}<br>
User Create (0.4ms) INSERT INTO "users" ("created_at", "updated_at") VALUES('2010-06-29 18:41:07', '2010-06-29 18:41:07')<br>
Completed in 13ms (View: 2, DB: 0) | 201 Created [http://localhost/users.xml]<br>
/Users/lukas/.rvm/rubies/ruby-1.9.2-preview3/lib/ruby/1.9.1/webrick/utils.rb:125: [BUG] Segmentation fault<br>
ruby 1.9.2dev (2010-05-31 revision 28117) [x86_64-darwin10.4.0]</p>
<h2>-- control frame ----------<br>
c:0005 p:---- s:0012 b:0012 l:000011 d:000011 CFUNC :(null)<br>
c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :now<br>
c:0003 p:0021 s:0007 b:0007 l:000e58 d:000006 BLOCK /Users/lukas/.rvm/rubies/ruby-1.9.2-preview3/lib/ruby/1.9.1/webrick/utils.rb:125<br>
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH<br>
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP</h2>
<p>-- Ruby level backtrace information ----------------------------------------<br>
/Users/lukas/.rvm/rubies/ruby-1.9.2-preview3/lib/ruby/1.9.1/webrick/utils.rb:125:in <code>block in initialize' /Users/lukas/.rvm/rubies/ruby-1.9.2-preview3/lib/ruby/1.9.1/webrick/utils.rb:125:in </code>now'<br>
^C</p>
<p>=end</p> Backport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=120752010-06-30T08:26:13Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>=begin<br>
Does it reproduce with the latest snapshot?<br>
=end</p> Backport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=121482010-07-05T22:18:41Zlukaso (Lukas Oberhuber)lukaso@gmail.com
<ul></ul><p>=begin<br>
I should have reported back sooner but was waiting to see if the problem reproduced.</p>
<p>The seg faults appear due to the sqlite3 gem. Since I've switched to the sqlite3-ruby gem, there have been no further segfaults.</p>
<p>I think this should be closed for now, and I will reopen if I get another crash.</p>
<p>Sorry for the disturbance.<br>
=end</p> Backport191 - Bug #3501: Segmentation Fault in vm_xmalloc (apparently)https://bugs.ruby-lang.org/issues/3501?journal_id=121492010-07-05T22:23:24Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Third Party's Issue</i></li></ul><p>=begin<br>
Okay, this ticket is set to "Third Party's Issue."<br>
Thanks!</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a><br>
=end</p>