On Apr 20, 2014, at 11:58 AM, Cody Garvin <c...@servalsoft.com> wrote:
> Second, while using instruments use the “mark heap” tool. Get your app up and > running. Mark the heap. Then start your image downloads, while that is > transpiring, mark the heap again. This will help narrow down the code that > could possibly be causing this. +1. Instruments has some great tools for this. I’m still learning my way around, but last time I was debugging a memory leak, I somehow got Instruments to show a graphical representation of the reference cycle. It literally drew me a f*ing diagram of where my bug was. Very impressive. (Is there any in-depth book on using Instruments? I’ve never been able to get much out of the Apple docs, they’re way too cursory.) —Jens _______________________________________________ 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
