Bug #22460: Ractor crash, shared arrays

• Status: Closed
• Assignee: eightbitraptor (Matt V-H)
• Target version: -
• Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN

[kddnewton (Kevin Newton)]

I'm sorry I have no idea what is going on with this, but this crashes:

a = Array.new(200, 0)
b = a.pop(150)
a << 0
b.freeze
Ractor.shareable?(b)

Replacing pop with slice! fixes it, if that helps.

[eightbitraptor (Matt V-H)]

• Assignee set to eightbitraptor (Matt V-H)

[eightbitraptor (Matt V-H)]

• Status changed from Open to Closed

Applied in changeset git|0d83a93784090400ce38f0852ae11bc103765810.

---

Unshare arrays only when they become shareable

obj_traverse_i called rb_ary_cancel_sharing on every array it visited,
before the traversal knew whether the object graph was shareable.

So Ractor.shareable? modified frozen arrays even when it returned false.

This commit moves rb_ary_cancel_sharing into mark_shareable, which
runs only after the traversal succeeds.

[Bug #22460]