From: Brian Candler <b.candler@...>
Date: 2009-02-27T04:58:15+09:00
Subject: Re: malloc error with String#<< / String#+

OK, I'm not a Mac expert I'm afraid.

ulimit -a

would be the first thing I'd try, to see what process memory and stack 
limits have been set, if any.

*** mmap(size=1073741824) failed (error code=12)

looks like something is asking to allocate exactly 1GB of RAM, which 
seems fishy to me. Maybe it's been growing this space and has now hit 
1GB.

If your Ruby process really is chewing up this much RAM (monitor it 
using 'top' while it runs), you'll need to find out why.

- building a data structure which is too big?

- holding onto references longer than you need?

- however there are some strange failure modes very occasionally (esp. 
with threads or continuations) where a phantom object reference remains 
in the stack area scanned by the GC, but is not really live. There have 
been some patches posted a while back which you could try.
-- 
Posted via http://www.ruby-forum.com/.