Segmentation fault after installing gems

[Maxattax97]

Description

I'm working on setting up Neovim with some plugins which require Ruby Gems. After installing RVM in the first boot of a freshly installed Antergos 17.7 x64 VM (which is snapshotted) I try to install a couple of gems, but am met with an ominous segmentation fault.

I personally know nothing about Ruby, but have done my best to carefully follow the installation instructions. I'd say maybe I'm doing something wrong, but I wouldn't expect to receive a segmentation fault for user error... An error message telling me I'm stupid would be appreciated though.

Steps to reproduce

1. Boot fresh install of Antergos 17.7 x64
2. $ gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB
3. $ curl -sSL https://raw.githubusercontent.com/wayneeseguin/rvm/stable/binscripts/rvm-installer | bash -s stable --ruby
4. $ source /home/max/.rvm/scripts/rvm
5. I've had this error both with and without the latest version, but for kicks we'll get the latest this time: $ rvm get master
6. I grab my environment variables for this bug report $ env
7. $ gem install neovim foodcritic erubi mdl puppet-lint reek rubocop slim_lint
8. Segmentation fault after "Installing ri documentation." This seems to be unrelated to the specific gem being installed.

Expected behavior

I expected to see that all of my gems were happily installed without a segmentation fault error.

Actual behavior

A segmentation fault occurs after "Installing ri documentation." Here are the outputs of commands 6 and 7:

• $ env
• $ gem install neovim foodcritic erubi mdl puppet-lint reek rubocop slim_lint

Debug mode:

• $ gem install neovim foodcritic erubi mdl puppet-lint reek rubocop slim_lint --debug

Environment info

[max@Maxattax-AntergosVM ~]$ rvm info

ruby-2.4.0:

  system:
    uname:        "Linux Maxattax-AntergosVM 4.11.9-1-ARCH #1 SMP PREEMPT Wed Jul 5 18:23:08 CEST 2017 x86_64 GNU/Linux"
    name:         "Arch"
    version:      "libc-2.25"
    architecture: "x86_64"
    bash:         "/usr/bin/bash => GNU bash, version 4.4.12(1)-release (x86_64-unknown-linux-gnu)"
    zsh:          " => not installed"
    remote_path:  "arch/libc-2.25/x86_64"

  rvm:
    version:      "1.29.2 (master)"
    updated:      "29 minutes 3 seconds ago"
    path:         "/home/max/.rvm"
    autolibs:     "[4] Allow RVM to use package manager if found, install missing dependencies, install package manager (only OS X)."

  ruby:
    interpreter:  "ruby"
    version:      "2.4.0p0"
    date:         "2016-12-24"
    platform:     "x86_64-linux"
    patchlevel:   "2016-12-24 revision 57164"
    full_version: "ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]"

  homes:
    gem:          "/home/max/.rvm/gems/ruby-2.4.0"
    ruby:         "/home/max/.rvm/rubies/ruby-2.4.0"

  binaries:
    ruby:         "/home/max/.rvm/rubies/ruby-2.4.0/bin/ruby"
    irb:          "/home/max/.rvm/rubies/ruby-2.4.0/bin/irb"
    gem:          "/home/max/.rvm/rubies/ruby-2.4.0/bin/gem"
    rake:         "/home/max/.rvm/rubies/ruby-2.4.0/bin/rake"

  environment:
    PATH:         "/home/max/.rvm/gems/ruby-2.4.0/bin:/home/max/.rvm/gems/ruby-2.4.0@global/bin:/home/max/.rvm/rubies/ruby-2.4.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/max/.rvm/bin"
    GEM_HOME:     "/home/max/.rvm/gems/ruby-2.4.0"
    GEM_PATH:     "/home/max/.rvm/gems/ruby-2.4.0:/home/max/.rvm/gems/ruby-2.4.0@global"
    MY_RUBY_HOME: "/home/max/.rvm/rubies/ruby-2.4.0"
    IRBRC:        "/home/max/.rvm/rubies/ruby-2.4.0/.irbrc"
    RUBYOPT:      ""
    gemset:       ""

[Maxattax97]

This issue is also occurring on my Arch Linux, which is not a VM. I've noticed that if I try to install packages one by one, this typically occurs with rubocop and reek. If I simply keep executing the command, eventually it will finish installing without a segmentation fault. I don't know if lingering files have resulted in a faulty but "successful" installation, or something else has happened.

[mpapis]

NOTE TO MYSELF: https://bugs.ruby-lang.org/issues/13150

[mpapis]

please try with:

rvm reinstall 2.4.0 --patch https://gist.githubusercontent.com/mpapis/da632ab8cd1af0ae158ec1cf75ab7080/raw/ade7df1d8ba4df4ef0918f9a4e6c9f9bad79b261/57954.patch