Try out vmmap against your (or some) application to see how things are
getting allocated. It can give you insights into how things are
working at the VM level.
[0:502] > vmmap iTunes
Virtual Memory Map of process 7842 (iTunes)
Output report format: 2.2 -- 32-bit process
Non-writable region
On Fri, Oct 31, 2008 at 1:28 AM, Michael Ash <[EMAIL PROTECTED]> wrote:
> Apparently it asks for 2MB at a time.
For tiny regions (for blocks <= 16 bytes), it looks like it appears to
allocate 1 MB chunks. For small regions (blocks <= 512 bytes), I think
it's around 8MB blocks. I think the 2 MB mu
> An internet search shows me that the error message...
>
> malloc: *** mmap(size=2097152) failed (error code=12)
>
> is quite common.
>
> What is the significance of the number 2097152, besides the fact that it is
> 2^21?
It's just the amount of memory in bytes it was trying to allocate when
it
On Thu, Oct 30, 2008 at 8:56 AM, Jerry Krinock <[EMAIL PROTECTED]> wrote:
>
> On 2008 Oct, 25, at 21:58, Ken Thomases wrote:
>
>> On Oct 25, 2008, at 11:48 PM, Jerry Krinock wrote:
>>
>>> Why did malloc say "No more!" on his Mac, but not on mine?
>>
>> Because you didn't let yours run amok for long
On 2008 Oct, 25, at 21:58, Ken Thomases wrote:
On Oct 25, 2008, at 11:48 PM, Jerry Krinock wrote:
Why did malloc say "No more!" on his Mac, but not on mine?
Because you didn't let yours run amok for long enough.
Thank you, Ken. I thought I did, but maybe I didn't.
If your app is leaking
On Oct 25, 2008, at 11:48 PM, Jerry Krinock wrote:
Why did malloc say "No more!" on his Mac, but not on mine?
Because you didn't let yours run amok for long enough.
If your app is leaking memory on a (more or less) continuous basis, it
will eventually get an error like your user got. You j
One of my users recently found conditions under the memory allocated
by my app would become huge. I fixed the problem, but I'm wondering
why it behaved differently for he and I.
On his MacBook Pro with Intel Core 2 Duo, 2 GB RAM, and 250 GB hard
drive with 160 GB free, it would crash after
