Issue #19387 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee set to ko1 (Koichi Sasada) ---------------------------------------- Bug #19387: Issue with ObjectSpace.each_objects not returning objects after starting a ractor https://bugs.ruby-lang.org/issues/19387#change-101680 * Author: luke-gru (Luke Gruber) * Status: Assigned * Priority: Normal * Assignee: ko1 (Koichi Sasada) * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- ```ruby r = Ractor.new do receive # block, the problem is not the termination of the ractor but the starting end ObjectSpace.each_object(IO) { |io| p io # we get no objects } ``` -- https://bugs.ruby-lang.org/

Issue #19387 has been updated by luke-gru (Luke Gruber). ruby -v set to 3.3.0 I believe this was closed prematurely due to an unrelated git commit that wrongly tagged it. Please reopen :) ---------------------------------------- Bug #19387: Issue with ObjectSpace.each_objects not returning objects after starting a ractor https://bugs.ruby-lang.org/issues/19387#change-106007 * Author: luke-gru (Luke Gruber) * Status: Closed * Priority: Normal * Assignee: ko1 (Koichi Sasada) * ruby -v: 3.3.0 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- ```ruby r = Ractor.new do receive # block, the problem is not the termination of the ractor but the starting end ObjectSpace.each_object(IO) { |io| p io # we get no objects } ``` -- https://bugs.ruby-lang.org/

Issue #19387 has been updated by Eregon (Benoit Daloze). One idea to solve this would be to implement `ObjectSpace.each_object` like TruffleRuby does it (at least when there are multiple Ractors): basically it's just the transitive `ObjectSpace.reachable_objects_from(roots)`. I.e. it uses the same mechanism as GC traversal/marking to find every object reachable from some roots objects (like `Object` class, the stack frames, etc). Context: the latest breakage due to this bug: https://github.com/ruby/prism/pull/3491 And I know of many before, it's a very common issue that `Ractor.new` can't be used in `make test-all`. ---------------------------------------- Bug #19387: Issue with ObjectSpace.each_objects not returning objects after starting a ractor https://bugs.ruby-lang.org/issues/19387#change-112275 * Author: luke-gru (Luke Gruber) * Status: Assigned * Assignee: ko1 (Koichi Sasada) * ruby -v: 3.3.0 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- ```ruby r = Ractor.new do receive # block, the problem is not the termination of the ractor but the starting end ObjectSpace.each_object(IO) { |io| p io # we get no objects } ``` -- https://bugs.ruby-lang.org/

Issue #19387 has been updated by osyoyu (Daisuke Aritomo). I also ran into this, so I opened an pull request document this behavior. https://github.com/ruby/ruby/pull/13278 ---------------------------------------- Bug #19387: Issue with ObjectSpace.each_objects not returning objects after starting a ractor https://bugs.ruby-lang.org/issues/19387#change-113039 * Author: luke-gru (Luke Gruber) * Status: Assigned * Assignee: ractor * ruby -v: 3.3.0 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- ```ruby r = Ractor.new do receive # block, the problem is not the termination of the ractor but the starting end ObjectSpace.each_object(IO) { |io| p io # we get no objects } ``` -- https://bugs.ruby-lang.org/