Yes, don't get me wrong, I trust the Apple docs, of course but I also know it's possible they are doing something wrong. I don't remember all cases but it always starts like this: I see something's not being freed, I try to free it, it doesn't work, I do a search on it and notice there are a lot of other developers saying this is an Apple bug and sending a bug report. One example is the IKImageBrowserNSImageRepresentationType used for the IKImageBrowserView. No one knows whether it's some kind of a very clever caching but for now it is not possible to completely remove the image of an NSImage-browserItem within an IKImageBrowserView.

What that means is -- I load like 100 images into my browser view, remove them, add another 200, remove them and the memory says 500 MBs or more. And that's nothing you can say 'Oh, don't worry it's all ok' about since my app's crashed this way. ;-) I guess, the reasons all other IKImageBrowserViews used in public 3rd party apps are working are a) the few images are too small for being a problem or b) the IKImageBrowserPathRepresentationType has been used which does the releasing very well.

But that's just one example, I mean no ones perfect that's why I make sure on my own that everything's fine. I've had a few classes in the past not behaving properly and being fixed in the next OS (Tiger to Leopard, Leopard to Snow Leopard…).

Best regards,
Tobias Jordan.

On Mar 13, 2010, at 5:52 PM, Alexander Spohr wrote:


Am 13.03.2010 um 17:41 schrieb Tobias Jordan:

I want to know what's going on inside my app and I've got enough experience in coding to know that just trusting the Apple docs (especially when it's about memory management) is not reliable.

Please explain this.

If you stick to the memory rules you’re fine.

        atze



_______________________________________________

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

Reply via email to