can't allocate region?

[Triston Whetten]

I personally have seen this type of issue (e.g. crashing with tclsh  
malloc() error) *many* times while upgrading outdated ports after a  
port sync.  I haven't paid attention to the error output.

I have noticed that watching via memory usage via 'top -o rprvt',  
python increases over time until it has 2GB private allocation and  
crashes.  I usually use 'port -Rfnuk upgrade outdated' to upgrade  
outdated ports.  When upgrade is done, I run 'port clean all'.

One case that I thinked caused this type of issue multiple times was  
upgrading gtk2 recently.  After a couple of hours the memory just  
begins to rapidly increase (rapidly is say 1.5GB allocated over 45  
minutes after running for 2 hours).  I wish I had more details to share.

Anything useful I could collect/observe that would be of use to shed  
some light on this?

Triston.


On May 27, 2008, at 7:27 PM, Rainer Müller wrote:

> Michael Hernandez wrote:
>> And as I write this I realize that my HD is also 100% full and that's
>> probably the cause of this. Sorry for the noise. That is a pretty  
>> ugly
>> error though, so it scared me. The malloc error made me think
>> something was wrong with my RAM.
>
> Ah, as I said in the other mail, this was ENOMEM. So I think the error
> occurred because the system couldn't get any more swap space.
>
> Rainer
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users