On Jun 10, 2013, at 10:23 AM, Jonathan Taylor wrote: > Thanks for your comments Ken.
You're welcome. > It was really good to learn about how to use heapshots effectively, that's > definitely something I'm going to use again in future. In this case it did > provide ~some~ more information on what is going on. > > Just to be clear, the problem is now solved by wrapping the correct bit of > code in an explicit autorelease pool, but I'm still very interested in > understanding what's going on and why Allocations is not reporting large > chunks of memory - I still maintain that this is not happening. If I > understood your reply correctly, you're saying this isn't what you would > expect. > However, if I understand you correctly, you are convinced that the (large) > backing buffer for the bitmap data should be being reported by Allocations. No, you've misunderstood. I was suggesting that there were large allocations that don't show up as objects. My theory was that they were not allocated via malloc but by something like vm_allocate(), which the Allocations instrument doesn't track. 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
