I can answer it myself: no, it should not be considered normal that an app leaks memory, and that is why it makes me quite nervous.
What happens is this: In an iPad / iPhone project I present a few UIImageViews on-screen. They are contained within their own UIScrollViews as I want to zoom in and out and scroll on them. I still have to work in the iOS Simulator because I am waiting for approval to provision my devices, but still testing seems to work fine. I can display images inside the views, and using keyboard modifiers I can emulate the standard gestures for zooming and scrolling, which al works perfectly. Sometimes, just sometimes, when I scroll an image beyond its content size (you can see the animating bouncing back and forth of the image inside the UIScrollView), Instruments reports a memory leak of only small number of bytes. These are not leaked images I created, it must be something deeper within the UIKit I guess. It tells me something like this: Leaked Object: Malloc 48 Bytes Address: any pointer to the leaked 48 Bytes Size: 48 Bytes Responsible Library: libsystem_c.dylib Responsible Frame: strdup Do you guys recognize this behavior? And should I get that nervous, or is it not an issue at all? (That is highly unlikely but I can ask, right?) Thank you for any insights. [[[Brainchild alloc] initWithName:@"Richard Altenburg"] saysBestRegards]; _______________________________________________ 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
