• 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: Greg Parker <email@hidden>
  • Date: Tue, 15 Oct 2013 15:31:20 -0700

On Oct 15, 2013, at 2:39 PM, Steve Mills <email@hidden> wrote:
> I don't think this is the case. I was seeing hundreds of still-alive allocated objects that came from the copied itemArray. I could clearly see a pattern in the Allocations sampling of Instruments of these objects, with the pattern repeating every time I did some user action in our app. And there was time between those actions, so if the autorelease pool wasn't getting any time to drain, there would be a much more serious issue at hand.

What does Instruments say about the retain/release history of the array object?

Are you running with Zombies enabled? Zombie mode prevents deallocation of every object.


--
Greg Parker     email@hidden     Runtime Wrangler



_______________________________________________

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


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>)

  • Prev by Date: Re: Cocoa class extension best practice
  • Next by Date: Re: Cocoa class extension best practice
  • Previous by thread: Re: Cocoa class extension best practice
  • Next by thread: Re: Cocoa class extension best practice
  • Index(es):
    • Date
    • Thread