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

ruby-talk
1

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

2

Please file a bug with a console log.

···

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).

--
Poor workers blame their tools. Good workers build better tools. The
best workers get their tools to do the work for them. -- Syndicate Wars

3

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

Poke at the results of `ulimit -a`.

···

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).