On 22 Apr, 2014, at 3:34 am, Dave <d...@looktowindward.com> wrote:

> Confusing results.
> 
> I changed the property in question:
> 
> @property (nonatomic,assign)          id                      payloadObject;
> 

Start with this - what do you want that property to be? 
Strong/weak/unsafe_unretained? 

Second - allocations, with our without heapshots, will tell you at least which 
objects are piling up. Heapshots are particularly good at this if you have an 
app you can move from one steady state to a memory-consuming one and back again 
where everything should release. Still probably best described here 
http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-find-undesirable-memory-growth/

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to