Segmentation fault with rails

[Ali Ismayilov]

Describe the bug
When using puma as rails server, I get segmentation fault. My app works fine with other web servers (webrick and thin tested).

Puma config:

# config/puma.rb
workers Integer(ENV['WEB_CONCURRENCY'] || 4)
threads_count = Integer(ENV['RAILS_MAX_THREADS'] || 5)
threads threads_count, threads_count

port        ENV['PORT']     || 3000
environment ENV['RACK_ENV'] || 'development'

preload_app!

on_worker_boot do
  # Worker specific setup for Rails 4.1+
  # See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
  ActiveRecord::Base.establish_connection
end

To Reproduce

Sadly, I can't share much of the codebase. The app is started with the following command:

$ rails s

It starts fine, but upon receiving any request crashes. Full crash report can be found here: https://gist.github.com/aliismayilov/bbfd82826202dc7e8c7b9913b5973799

Expected behavior
Serve requests without crashing.

Desktop (please complete the following information):

• OS: macOS Ventura 13.4 (22F66)
• Puma version: 6.3.0
• Ruby version: 3.2.2

Please let me know if I can provide more insight.