• 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: Cocoa class extension best practice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa class extension best practice


  • Subject: Re: Cocoa class extension best practice
  • From: Ken Thomases <email@hidden>
  • Date: Wed, 16 Oct 2013 10:08:03 -0500

On Oct 16, 2013, at 9:38 AM, Steve Mills wrote:

> On Oct 16, 2013, at 00:28:17, Ken Thomases <email@hidden> wrote:
>
>> Regarding the general issue of the mystery objects that are still alive, there's little point in speculating.  Look at the object's history in the Allocations instrument to see not only where it was allocated but all retains, releases, and autoreleases.  Correlate those until you see which code had a responsibility to release but failed to.
>
> Ah, that helps. Yes, it looks like all of these allocations coming from itemArray are being released.

Released to the point of being deallocated?  Deallocation would also be indicated in the history.

> I'm confused, then, by what the Live column denotes when looking at the All Allocations or __NSArrayI detail, because it shows a bullet in that column for *every* __NSArrayI that was allocated by itemArray - all 8000+ of them appear to be still living by the end of the app's run. The docs for this instrument says the Live column means "Denotes if the object is currently live."

Yes, my understanding is that "live" means not yet deallocated, too.

Regards,
Ken


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Cocoa class extension best practice
      • From: Steve Mills <email@hidden>
References: 
 >Cocoa class extension best practice (From: Steve Mills <email@hidden>)
 >Re: Cocoa class extension best practice (From: Kyle Sluder <email@hidden>)
 >Re: Cocoa class extension best practice (From: Steve Mills <email@hidden>)
 >Re: Cocoa class extension best practice (From: Graham Cox <email@hidden>)
 >Re: Cocoa class extension best practice (From: "Mills, Steve" <email@hidden>)
 >Re: Cocoa class extension best practice (From: Graham Cox <email@hidden>)
 >Re: Cocoa class extension best practice (From: Steve Mills <email@hidden>)
 >Re: Cocoa class extension best practice (From: Jens Alfke <email@hidden>)
 >Re: Cocoa class extension best practice (From: Ken Thomases <email@hidden>)
 >Re: Cocoa class extension best practice (From: Steve Mills <email@hidden>)

  • Prev by Date: Converting views to use layer backing
  • Next by Date: Re: Core Data with ODBC databases?
  • Previous by thread: Re: Cocoa class extension best practice
  • Next by thread: Re: Cocoa class extension best practice
  • Index(es):
    • Date
    • Thread