'gem update --system' runnaways? requires more than 120mb memory?

Discussion in 'Ruby' started by Mark T, Sep 23, 2007.

  1. Mark T

    Mark T Guest

    Is there a good/bad reason 'gem update --system' would gobble up all
    available memory then halt with message 'killed' to the console?
    (122072k free).

    ATB,

    MarkT
    Mark T, Sep 23, 2007
    #1
    1. Advertising

  2. Mark T

    Eric Hodel Guest

    On Sep 22, 2007, at 21:03, Mark T wrote:
    > Is there a good/bad reason 'gem update --system' would gobble up all
    > available memory then halt with message 'killed' to the console?
    > (122072k free).


    Please file a bug with a console log.

    --
    Poor workers blame their tools. Good workers build better tools. The
    best workers get their tools to do the work for them. -- Syndicate Wars
    Eric Hodel, Sep 23, 2007
    #2
    1. Advertising

  3. Mark T

    Ryan Davis Guest

    On Sep 22, 2007, at 21:03 , Mark T wrote:

    > Is there a good/bad reason 'gem update --system' would gobble up all
    > available memory then halt with message 'killed' to the console?
    > (122072k free).


    'killed' kinda sounds like OS process limits were tripped...

    Poke at the results of `ulimit -a`.
    Ryan Davis, Sep 25, 2007
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Austin 7873
    Replies:
    5
    Views:
    176
    Eric Hodel
    Jan 27, 2007
  2. Brian Puccio
    Replies:
    3
    Views:
    378
    John Joyce
    Mar 3, 2008
  3. Iñaki Baz Castillo
    Replies:
    1
    Views:
    145
    Iñaki Baz Castillo
    Feb 28, 2011
  4. Steven D'Aprano
    Replies:
    0
    Views:
    75
    Steven D'Aprano
    Dec 23, 2013
  5. Replies:
    3
    Views:
    69
    Gary Herron
    Dec 23, 2013
Loading...

Share This Page