I have used memory-profiler tools on other platforms and languages, and most have a concept of "registering expected memory leaks". I haven't seen any indication that Instruments knows that Cocoa.framework has expected memory leaks, nor any way to force those expected memory leaks to be cleaned up, perhaps as an #ifdef block of code, to be used when you want to simplify memory leak profiling only.
I'm a relatively new user of XCode and relatively new to Cocoa programming, although I have dabbled in Cocoa and Mac OS X programming back when it was *Project Builder *in the pre-XCode days. I posted this question on StackOverflow today: http://stackoverflow.com/questions/14346955/empty-new-cocoa-mac-os-x-application-leaks-14799-items-right-out-of-the-box-in In short, it feels to me like I'm drowning in "too much information" from Instruments, which tells me even about the framework leaks that are probably expected, and "no information at all" from the Static Analysis features. I feel like I probably have missed some important documentation somewhere that would enlighten me. Warren Postma RentalPoint Software _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
