On Fri, Apr 25, 2014, at 01:16 PM, edward taffel wrote: > thanks kyle, > > if this were the case, i should expect to see the same report for both > scrollers;
Not necessarily. If they were both deallocated on the same background thread, then there's only one thread with a dangling CATransaction to complain about. > as they are allocated & released at the same code points, & i > don’t pass the references around. but, i’ll do some checking to be sure. > One insidious possibility is a block submitted to a background queue via dispatch_async that captures a reference to some object that has a chain of pointers that winds up at a view. For example, NSDocument is a prime contender: it itself doesn't have any UI, but it owns its window controllers, which own their windows, which own their view hierarchies. If an NSDocument is deallocated on a background thread, the views might be deallocated on a background thread as well. --Kyle Sluder _______________________________________________ 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
