Iphone SDK Utility Application template has leak Iphone SDK Utility Application template has leak objective-c objective-c

Iphone SDK Utility Application template has leak


That might be a leak or it might not be a leak. If you were to add the backtrace of the allocation, that would be helpful.

More likely than not, it isn't a leak, but some bookkeeping information that is being stashed away by dyld that leaks/Instruments loses track of.

Given that it is 128 bytes and I'm guessing there is only one of them, I would encourage you to file a bug via http://bugreport.apple.com and then forget about it for now as, in the unlikely case that it really is a leak, you will be equally as unlikely to be able to fix it from within your application.


Hope this helps.

From: http://www.cocos2d-iphone.org/forum/topic/2460

"The simulator has bugs related to singletons and llvm stuff that are incorrectly reported by Instruments. Always check your leaks on the device itself."


Got the leak doing this:

XCode 3.2--

File, New Project, Navigation-based Application
Give it a name
Build It
Run With Performance Tools -> Leaks

When Instruments comes up, click on Leaks (you might have to click the little icon at the bottom that looks like four boxes within a box)

About 7 seconds after running you should see the leak:-- Malloc 128 Bytes, some Address, 128 Bytes, CoreGraphics, open_handle_to_dylib_path

I traced it to this code in the AppDelegate:

//APPLE CODE- (void)applicationDidFinishLaunching:(UIApplication *)application {        // Override point for customization after app launch        [window addSubview:[navigationController view]];    [window makeKeyAndVisible];}

I broke out the navigationController (did a separate alloc and release) and COMMENTED OUT the addSubview: action - there was no leak - and, obviously, the screen was blank.

It wasn't until I attempted addSubview that the leak occurred. Since there are numerous ways to add a subview, I tried those. Each resulted in the leak or a blank screen.