On Feb 18, 2011, at 3:00 PM, Mr. Gecko wrote: > I noticed that memory is not autoreleased when I receive a distributed > notification, the only way to fix this is to wrap it in a autorelease pool, > but this shouldn't be right? I would think that when you register for a > notification it'll be on the run loop which has a autorelease pool and > therefore shouldn't leak, instruments doesn't see these allocations as a > leak, but you can see they are still alive.
Is your application getting any real GUI-style events, or is it only receiving the distributed notifications? It's very possible that the main event loop's autorelease pool is only drained after processing a real event and not necessarily for every thing that's called out for a run loop source. Regards, Ken _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com