Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault for Ruby 3.0 #18

Closed
sveredyuk opened this issue Jan 8, 2021 · 5 comments
Closed

Segmentation fault for Ruby 3.0 #18

sveredyuk opened this issue Jan 8, 2021 · 5 comments

Comments

@sveredyuk
Copy link

Hi, seems like I found segfault for Ruby 3.0

When trying to load rails 6.1.1 environment:

/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activerecord-pg_enum-1.2.2/lib/active_record/pg_enum/postgresql_adapter.rb:5: [BUG] Segmentation fault at 0x0000000300000004
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.
@alassek
Copy link
Owner

alassek commented Feb 5, 2021

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.

@RobertGauld
Copy link

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.

@alassek
Copy link
Owner

alassek commented Apr 11, 2021

I've adding Ruby 3.0.1 to CI, and so far have not been able to reproduce this. Can any of you?

@RobertGauld
Copy link

It appears to have been behaving recently, possibly some tool/library from elsewhere got updated.

@alassek
Copy link
Owner

alassek commented May 27, 2021

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.

@alassek alassek closed this as completed May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants