• 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: Leaks question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Leaks question


  • Subject: Re: Leaks question
  • From: Lorenzo Thurman <email@hidden>
  • Date: Mon, 10 Dec 2007 11:41:21 -0600

j o a r wrote:

On Dec 10, 2007, at 9:03 AM, Lorenzo Thurman wrote:

Thanks, I think this is what I'm looking for. Leaks points to the function, ObjectAlloc shows the various leaked objects, but I'm still playing 20 questions figuring out which line or object is causing the leak.


The backtrace to the allocation event is one data point for sure, and a good place to start, but the allocation is in many cases not the memory management event that causes the leak.

Like I hinted at earlier: You can configure ObjectAlloc / the Object Allocations instrument to record all memory management events (alloc, retain, release, et.c.). This typically takes all remaining guesswork out of the equation.

j o a r


Thanks, I'll look there again also.
_______________________________________________
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


References: 
 >Leaks question (From: Lorenzo Thurman <email@hidden>)
 >Re: Leaks question (From: j o a r <email@hidden>)
 >Re: Leaks question (From: Rick Altherr <email@hidden>)
 >Re: Leaks question (From: Lorenzo Thurman <email@hidden>)
 >Re: Leaks question (From: j o a r <email@hidden>)

  • Prev by Date: Re: Leaks question
  • Next by Date: Re: subversion reference
  • Previous by thread: Re: Leaks question
  • Next by thread: Re: Leaks question
  • Index(es):
    • Date
    • Thread