Skip to content

Fix allocation count when forking with Ractors #13286

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 1 commit into from
May 9, 2025

Conversation

jhawthorn
Copy link
Member

@jhawthorn jhawthorn commented May 9, 2025

This fixes a test when run with GC assertions introduced in #12982. After fork we reset to single ractor mode (which IMO we shouldn't do, but it requires more work to fix) and so we need to add the pending object counts back to the main heap.

cc @ko1
cc @etiennebarrie @byroot I think this was even more broken before #13192, this tweak just makes it so the count ends up correct again for single-ractor-mode after a fork

After fork we reset to single ractor mode (which IMO we shouldn't do,
but it requires more work to fix) and so we need to add the pending
object counts back to the main heap.
Copy link

launchable-app bot commented May 9, 2025

All Tests passed!

✖️no tests failed ✔️61683 tests passed(1 flake)

@jhawthorn jhawthorn merged commit 30ef0f1 into ruby:master May 9, 2025
84 checks passed
byroot added a commit to byroot/ruby that referenced this pull request May 9, 2025
byroot added a commit that referenced this pull request May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants