From: "nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@...>
Date: 2025-02-19T10:11:12+00:00
Subject: [ruby-core:121123] [Ruby master Bug#21149] Strange behavior of ObjectSpace.each_object after Ractor.new

Issue #21149 has been updated by nobu (Nobuyoshi Nakada).


Interesting.
It seems irrelevant what is done in the new Ractor.
Even if the block is empty, the result is same.

----------------------------------------
Bug #21149: Strange behavior of ObjectSpace.each_object after Ractor.new
https://bugs.ruby-lang.org/issues/21149#change-112045

* Author: wanabe (_ wanabe)
* Status: Open
* ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
I found the strange behavior of `ObjectSpace.each_object`.
It misses some objects after `Ractor.new`.

```
$ ruby -ve 'class Foo; end; foo = Foo.new; Ractor.new do buz = Foo.new end.take; bar = Foo.new; p [ObjectSpace.each_object(Foo).to_a, foo.class, bar.class]'
ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
-e:1: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.
[[], Foo, Foo]
```

Of course it works well without `Ractor.new`.

```
$ ruby -ve 'class Foo; end; foo = Foo.new; bar = Foo.new; p [ObjectSpace.each_object(Foo).to_a, foo.class, bar.class]'
ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
[[#<Foo:0x00007fa84f4b26d0>, #<Foo:0x00007fa84f4b27c0>], Foo, Foo]
```



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/