Bug #18023: Ractor#make_shareable changes the values of closured shareable objects - Ruby master - Ruby Issue Tracking System

Actions

Updated by slowpilot (Ivan Razuvaev) almost 3 years ago

slowpilot (Ivan Razuvaev) wrote:

Hi. I encountered strange behaviour or shareable procs when every even closured shareable variable becomes the FalseClass instance.

[usr@srvr ~]$ irb
3.0.1 :001 > v1, v2, v3, v4 = :a, :b, :c, :d
 => [:a, :b, :c, :d] 
3.0.1 :002 > p = Proc.new { p v1, v2, v3, v4 }
 => #<Proc:0x000000000248ed18 (irb):2> 
3.0.1 :003 > p.()
:a
:b
:c
:d
 => [:a, :b, :c, :d] 
3.0.1 :004 > Ractor.make_shareable(p).()
:a
false
:c
false
 => [:a, false, :c, false]

This is stopping from using dynamically defined methods from ractors. E.g. in Ruby libtorch. So after calling rb_ext_ractor_safe in extension, I am trying to do something like:

cls.define_singleton_method('new', Ractor.make_shareable(Proc.new { ... })

That leads to every second closure assignment to false.

Actions

Copy link

#2

Updated by alanwu (Alan Wu) over 2 years ago

Status changed from Open to Closed

Applied in changeset git|76228191474c76810043b294a74bbb2f1808b3d9.

Fix Ractor.make_shareable changing locals for Procs

env_copy() uses rb_ary_delete_at() with a loop counting up while
iterating through the list of read only locals. rb_ary_delete_at() can
shift elements in the array to an index lesser than the loop index,
causing locals to be missed and set to Qfalse in the returned
environment.

Iterate through the locals in reverse instead, this way the shifting
never happens for locals that are yet to be visited and we process all
the locals in the array.

[Bug #18023]

Actions

Copy link

#3