Ruby Issue Tracking System

01/03/2026

02:19 AM Ruby Bug #21819 (Closed): A Data object should be frozen even if it has no members

Data objects with at least one member are currently automatically frozen on construction, and shareable if all members are shareable. However, a Data object with no members is not frozen on construction. I would expect such an object sim... dazuma (Daniel Azuma)

01/02/2026

07:02 PM Ruby Bug #21818 (Assigned): Thread backtraces cannot be communicated over Ractor ports

It looks like Thread::Backtrace is confined to the Ractor that produced it: it cannot be copied or moved to another Ractor, nor can it be made shareable. This makes it difficult for a Ractor to communicate exceptions (e.g. the reason for... dazuma (Daniel Azuma)

11/13/2023

11:01 PM Ruby Bug #18129: Ractor-incompatible global variables can be accessed through alias

I've tried a number of different variations on this, but never got it to reproduce (tried `ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-darwin22]` and `ruby 3.0.6p216 (2023-03-30 revision 23a532679b) [x86_64-darwin22]` since the o... dazuma (Daniel Azuma)

10:45 PM Ruby Bug #18119: Ractor crashes when instantiating classes

Reproduces in 3.2.2 (MacOS 14 on x86_64). Again different error message:
```
ruby(17800,0x7000094bd000) malloc: Heap corruption detected, free list is damaged at 0x60000271cfe0
*** Incorrect guard value: 0
```
dazuma (Daniel Azuma)

10:41 PM Ruby Bug #18024: Ractor crashes when connections are closed in multiple Ractors

Also not able to reproduce on `ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-darwin22]` or `ruby 3.3.0dev (2023-11-13T21:00:10Z master e8ab3f7010) [x86_64-darwin23]`. I wonder if this was an environment issue in the original report. dazuma (Daniel Azuma)

10:03 PM Ruby Bug #17624: Ractor.receive is not thread-safe

Retested, still reproduces on 3.2.2 and 3.3.0-dev as of 2023 Nov 13.
dazuma (Daniel Azuma)

09:59 PM Ruby Bug #17617: When a Ractor's incoming port is closed, Ractor.receive_if does not raise Ractor::ClosedError, but instead blocks indefinitely

Retested, still reproduces on 3.2.2 and 3.3.0-dev as of 2023 Nov 13. dazuma (Daniel Azuma)

02/13/2021

02:14 AM Ruby Bug #17624 (Closed): Ractor.receive is not thread-safe

It does not seem to be possible to have multiple blocked `Ractor.receive` calls concurrently in the same Ractor (but different threads). One may succeed but the others will hang indefinitely, even if messages are present in the queue.
... dazuma (Daniel Azuma)

02/09/2021

04:24 PM Ruby Bug #17617 (Closed): When a Ractor's incoming port is closed, Ractor.receive_if does not raise Ractor::ClosedError, but instead blocks indefinitely

If Ractor#close_incoming is called on a Ractor, any pending Ractor.receive call will raise Ractor::ClosedError. However, any pending Ractor.receive_if call will not; instead, it never returns.
```
r1 = Ractor.new do
Ractor.receive... dazuma (Daniel Azuma)

01/04/2021

06:40 AM Ruby Feature #10499: Eliminate implicit magic in Proc.new and Kernel#proc

Note that the documentation still specifies the old behavior in 3.0.0.
> Creates a new Proc object, bound to the current context. ::new may be called without a block only within a method with an attached block, in which case that bloc... dazuma (Daniel Azuma)