Segmentation fault at 0x0000000000000000

Open
#426 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
backend

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.

Description

bug

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

  1. When every I reinstall ruby RUBY_CONFIGURE_OPTS="--enable-yjit" ruby-build 3.2.2 ~/local/ruby/3.2.2
  2. Install all gems bundle install
  3. The rails server fail to start `bin/rails s -p3001

rails-vips-crash.log

Expected behavior
Rails server should start.

Desktop:

  • OS: MacOS Ventura 13.7.8
Dominant language
Ruby
Stars
904
Forks
64
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libvips/ruby-vips

All issues in libvips/ruby-vips

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.