Closed sveredyuk closed 3 years ago
I've seen this happen in CI but haven't been able to repro locally so far. The line of code that is segfaulting is a totally standard module include, so I don't have the slightest idea what could be going wrong here.
Me too. Rails 6.1.3, Ruby 3.0.0p0. Unfortunately very intermittent. Most of the time an uninstall then install of the gem works to clear it.
I've adding Ruby 3.0.1 to CI, and so far have not been able to reproduce this. Can any of you?
It appears to have been behaving recently, possibly some tool/library from elsewhere got updated.
I'm going to close this for now, if someone can provide reproduction steps I'll take a closer look. My gut tells me this was probably a bug in 3.0.0 that got patched. There is no legitimate reason for a module include to segfault.
Hi, seems like I found segfault for Ruby 3.0
When trying to load rails 6.1.1 environment: