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

Ruby
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

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.

3

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.