https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-02-23T20:36:32ZRuby Issue Tracking SystemRuby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=905652021-02-23T20:36:32Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Assignee</strong> set to <i>k0kubun (Takashi Kokubun)</i></li></ul><p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/572">@hsbt (Hiroshi SHIBATA)</a> Does this error occur without <code>-j</code> (e.g. without JIT support)? Is it possible to provide a self contained example?</p> Ruby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=921232021-05-23T00:08:45Zk0kubun (Takashi Kokubun)takashikkbn@gmail.com
<ul></ul><p>mjit_compile.c:525 of Ruby 3.0.0 is the only hint about this error, but it seems like a race condition with GC of child ISeqs. I guess this could happen because mjit_mark only marks <code>compiling_iseq</code>. We probably need to mark children as well.</p> Ruby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=921262021-05-23T00:52:13Zk0kubun (Takashi Kokubun)takashikkbn@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li></ul> Ruby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=922812021-05-31T04:42:21Zk0kubun (Takashi Kokubun)takashikkbn@gmail.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>Applied in changeset <a class="changeset" title="Mark inlined ISeqs during MJIT compilation (#4539) [Bug #17584]" href="https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/1aac0e88193a82ed36b43e852c46414181b66455">git|1aac0e88193a82ed36b43e852c46414181b66455</a>.</p>
<hr>
<p>Mark inlined ISeqs during MJIT compilation (<a class="issue tracker-2 status-2 priority-4 priority-default" title="Feature: Array#zip_with (Assigned)" href="https://bugs.ruby-lang.org/issues/4539">#4539</a>)</p>
<p>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Segmentation fault with Ruby 3.0 (Closed)" href="https://bugs.ruby-lang.org/issues/17584">#17584</a>]</p> Ruby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=929302021-07-16T13:10:23Znagachika (Tomoyuki Chikanaga)nagachika00@gmail.com
<ul><li><strong>Backport</strong> changed from <i>2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN</i> to <i>2.7: DONTNEED, 3.0: REQUIRED</i></li></ul> Ruby master - Bug #17584: Segmentation fault with Ruby 3.0https://bugs.ruby-lang.org/issues/17584?journal_id=929322021-07-18T02:02:45Znagachika (Tomoyuki Chikanaga)nagachika00@gmail.com
<ul><li><strong>Backport</strong> changed from <i>2.7: DONTNEED, 3.0: REQUIRED</i> to <i>2.7: DONTNEED, 3.0: DONE</i></li></ul><p>already backported at 9680ee97e0b3e87c0fc9a65c01de1ee50a1a178b.<br>
ref. <a href="https://bugs.ruby-lang.org/issues/17928" class="external">https://bugs.ruby-lang.org/issues/17928</a></p>