@david and I found the root cause. (similar to what @Falco found in the past)
We use special Ruby flags to try to limit memory during upgrades and this no longer works on Ruby 3.2.
We should have a PR shortly to fix the issue.
7 Likes