Segmentation fault at 0x0000000000000000
Open
Nobody has claimed this yet.
bug
- Dominant language
- Ruby
- Stars
- 904
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I upgraded my ruby version to 3.2.2 for my rails application and since then it is not possible to boot the server anymore.
To Reproduce
- When every I reinstall ruby
RUBY_CONFIGURE_OPTS="--enable-yjit" ruby-build 3.2.2 ~/local/ruby/3.2.2 - Install all gems
bundle install - The rails server fail to start `bin/rails s -p3001
Expected behavior
Rails server should start.
Desktop:
- OS: MacOS Ventura 13.7.8
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading rails-vips-crash.log and reproducing the failure with Ruby 3.2.2, YJIT enabled, and the reported bundle on macOS Ventura. Compare the failing boot path from bin/rails s -p3001 with a configuration that starts successfully; done means the Rails server boots without the segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100