I assumed that ISeq is never GC-ed by in_jit + mjit_mark on copy job ISeq, but unfortunately I found SEGV on mjit_copy_job_handler in which iseq->body was somehow Qnil. And it seems to be fixed by disabling the job when mjit_free_iseq is called for the ISeq.
Added by k0kubun (Takashi Kokubun) over 6 years ago
Do not execute MJIT copy job when ISeq is GC-ed
I assumed that ISeq is never GC-ed by
in_jit+mjit_markon copy jobISeq, but unfortunately I found SEGV on
mjit_copy_job_handlerin whichiseq->body was somehow Qnil. And it seems to be fixed by disabling the
job when
mjit_free_iseqis called for the ISeq.git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67551 b2dd03c8-39d4-4d8f-98ff-823fe69b080e