Closed ttanimichi closed 6 months ago
@ttanimichi Sorry you're having a problem, I'll try to help.
This command:
rails new --css=tailwind --javascript=esbuild segv_ruby330_tailwind
does not add tailwindcss-rails
to your app (check your Gemfile). The stack trace in the crash report does not include any code from tailwindcss-rails
.
Can you help me understand why you think this gem is causing the problem you're seeing?
I think you're right that https://bugs.ruby-lang.org/issues/20085 is the root cause here; the line in concurrent-ruby that segfaulted is
Fiber.new { mutex.owned? }.resume
so I'm going to close this as unrelated to tailwindcss-rails. Hopefully the fix gets released in ruby 3.3.1 soon! :crossed_fingers:
Oh? I didn't realize that the latest version of Rails no longer uses tailwindcss-rails (I thought Rails used to depend on it)
repo: https://github.com/ttanimichi/segv_ruby330_tailwind
This ticket might be related. The steps to reproduce are as follows: