Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Disable GC when building id2ref table #13346

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 15, 2025
Merged

Conversation

casperisfine
Copy link
Contributor

Building that table will likely malloc several time which can trigger GC and cause race condition by freeing objects that were just added to the table.

Disabling GC to prevent the race condition isn't elegant, but iven this is a deprecated callpath that is executed at most once per process, it seems acceptable.

Hoping this will fix http://ci.rvm.jp/results/master@oci-aarch64/5755835 (FYI @ko1)

Building that table will likely malloc several time which
can trigger GC and cause race condition by freeing objects
that were just added to the table.

Disabling GC to prevent the race condition isn't elegant,
but iven this is a deprecated callpath that is executed at
most once per process, it seems acceptable.
@byroot byroot requested a review from peterzhu2118 May 15, 2025 11:26
@byroot byroot merged commit 31ba881 into ruby:master May 15, 2025
83 checks passed
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.

3 participants