Skip to content

Remove rb_gc_start from cancel_single_ractor_mode #13047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 3, 2025

Conversation

jhawthorn
Copy link
Member

In 307732c Ractors were changed to explicitly run GC when the first non-main one was activated in order to disable the transient heap. Theap no longer exists so I don't think we need to do this.

Copy link

launchable-app bot commented Apr 2, 2025

All Tests passed!

✖️no tests failed ✔️61916 tests passed(3 flakes)

jhawthorn and others added 2 commits April 3, 2025 08:32
T_DATA with a NULL pointer are not marked. Let's wrap 1 instead to
ensure that our mark function is actually run.
In 307732c Ractors were changed to
explicitly run GC when the first non-main one was activated in order to
disable the transient heap. Theap no longer exists so I don't think we
need to do this.
@jhawthorn jhawthorn force-pushed the no_gc_on_first_ractor branch from d08adf1 to 33114a1 Compare April 3, 2025 15:36
@jhawthorn jhawthorn merged commit 137b51e into ruby:master Apr 3, 2025
75 checks passed
@jhawthorn jhawthorn deleted the no_gc_on_first_ractor branch April 3, 2025 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant