• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: leak detecting vs memory
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: leak detecting vs memory


  • Subject: Re: leak detecting vs memory
  • From: David Dunham <email@hidden>
  • Date: Thu, 1 Dec 2005 13:24:16 -0800

At 22:14 +0100 05-12-01, j o a r wrote:

I routinely like to leave MallocStackLogging set (in the info dialog for my executable), so I can perform leak detection whenever I feel like it. However, I went out to lunch, and got

Acropolis-D(419,0xa000ed68) malloc: *** out of memory while stack logging
Program received signal:  "SIGABRT".

This is why I asked my boss for all the memory that would fit in my machine! And got it! :-)

Only 1.25 GB, but I would have thought there was plenty of VM available.

Oh wait, right after I typed that, it happened again. And there's still 2.74 GB free on the startup disk.
--


David Dunham     A Sharp, LLC
Voice/Fax: 206 783 7404     http://a-sharp.com
Efficiency is intelligent laziness.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: leak detecting vs memory
      • From: j o a r <email@hidden>
References: 
 >leak detecting vs memory (From: David Dunham <email@hidden>)
 >Re: leak detecting vs memory (From: j o a r <email@hidden>)

  • Prev by Date: Re: leak detecting vs memory
  • Next by Date: Re: leak detecting vs memory
  • Previous by thread: Re: leak detecting vs memory
  • Next by thread: Re: leak detecting vs memory
  • Index(es):
    • Date
    • Thread