Not signed in (Sign In)

Ruby + Rails: [Sink] [Advisory] Do not update Gem to 1.1.1

Bottom of Page

1 to 12 of 12

  1.  
    •  
      CommentAuthorSuperJared
    • CommentTimeApr 11th 2008
     permalink
    After receiving several complaints in our chat room, we've concluded that Gem v1.1.1 has a significant memory leak and will likely not finish any task properly on a 256slice, and will likely take several hours to complete on a 512slice.

    If you have already upgraded, we recommend installing version 1.1.0 instead, as it does not have this issue.
    •  
      CommentAuthorSuperJared
    • CommentTimeApr 14th 2008
     permalink

    I have a feeling it has something to do with this

    • CommentAuthorDru
    • CommentTimeApr 15th 2008
     permalink

    Interesting, I’ve been running 1.1.1 since it first came out and I’ve yet to have a problem on my 256mb slice. Everything finishes in a matter of seconds. Although I’ve been running gem update daily via a cronjob so that I avoid having a build up of metadata that has to be updated so maybe that’s why I’ve avoided it.

    • CommentAuthormyobie
    • CommentTimeMay 29th 2008 edited
     permalink

    http://rubyforge.org/frs/?group_id=126

    There you can get any release you want. 1.1.1 is driving me mad.

    Requiring more than 256mb of ram just for a package manager is ridiculous.

    •  
      CommentAuthorJC Denton
    • CommentTimeMay 31st 2008
     permalink
    Posted By: Dru

    Interesting, I’ve been running 1.1.1 since it first came out and I’ve yet to have a problem on my 256mb slice. Everything finishes in a matter of seconds.


    I can second that. I'm running the Portage version of 1.1.1 on a 512mb slice.
    • CommentAuthorSchultz
    • CommentTimeJun 1st 2008 edited
     permalink
    i currently have it running on my development machine that only has 128megs of ram and don't have any issues with it either.

    Hum finally updated it on my slice and its going slow and chewing up the memory. While my development box 128meg Gentoo install has no issues with it. Wonder if its something with 64bit ruby version. That is the only difference is the arch.
  7.  permalink

    First of all, at the time of writing RubyGems is at version 1.1.1. If you have this version there is a known bug which causes RubyGems to get confused when bulk updating; meaning high load usage, high memory usage, high swap usage. Downgrade to version 1.1.0 and these problems appear to disappear.

    I personally downgraded by manually downloading the RubyGems v1.1.0 zip file from here: http://rubyforge.org/frs/?group_id=126 . I then FTP’d this file to my server that ran the following:

    unzip rubygems-1.1.0.zip cd rubygems-1.1.0/ sudo ruby ./setup.rb (you have to provide your root password for the sudo command)

    This gives a warning but you can ignore it because gem is symlinked to 1.1.0 instead of 1.1.1 now. You can test this by:

    gem -v 1.1.0

    Now to upgrade to Rails 2.1.0 which is what I set out to do before getting embroiled in this situation, I ran the following commands:

    sudo gem update --no-update-sources activeresource sudo gem update --no-update-sources activerecord sudo gem update --no-update-sources actionpack sudo gem update --no-update-sources actionmailer sudo gem update --no-update-sources rails

    Hope this works for you all.

    • CommentAuthordlrush
    • CommentTimeJun 18th 2008 edited
     permalink
    While this didn't solve the problem on a 256 slice, it did after upgrading to a 512 (centos5):

    Install this patch to 1.1.1:
    http://blog.evanweaver.com/articles/2008/05/26/rubygems-memory-patch

    Then run gem with the --no-rdoc and --no-ri options:
    >gem install --no-rdoc --no-ri rails
    •  
      CommentAuthorSuperJared
    • CommentTimeJun 20th 2008
     permalink
  10.  permalink
    Hi,

    Just spreading the word that the latest version (1.2.0) has FIXED the memory issues experienced when installing and updating on smaller Slices.

    I have updated the articles site and rubygems articles to reflect the new release:

    http://articles.slicehost.com/2008/4/30/ubuntu-hardy-ruby-on-rails

    I hope that helps and thanks to Jared and all those who tested the new version!

    Cheers, PickledOnion
    • CommentAuthorjohnny99
    • CommentTimeOct 26th 2008
     permalink
    I updated to 1.2.0 and am still experiencing the same problem. It's maddening to have your slice grind to a halt for hours every time you do a simple 'gem install rails'. Tried all the suggestions here and elsewhere, nothing has helped.
  12.  permalink

    Give this a try:

    1. gem install rubygems-update 2. update_rubygems

    (ref. http://sumanthtechsavvy.blogspot.com/2008/12/tweak-updating-ruby-gems.html)

    Has gotten me out of a bind from 1.2 up to 1.3.x on two slices…

1 to 12 of 12

  1.