Open Radar

 
The Xcode templates for new iPhone applications create an NSAutoreleasePool in their main() function. This is wrong, as any object released without a pool will end up in this autorelease pool, which persists for the entire duration of the application. So effectively the object is still leaked.

Usually, if there is no autorelease pool in place, the runtime logs an error message about the missing pool and tells the developer to set a breakpoint on _NSAutoreleaseNoPool to find where the pool-less autorelease happens. The top-level NSAutoreleasePool as found in the templates thus actually *hides* this leak from the users.

UIApplicationMain() should build its own autorelease pool as needed. If someone thinks they really need to run ObjC code before calling UIApplicationMain() (and they can't do the same work in applicationDidFinishLaunching: or the likes), they can always create a pool *before* UIApplicationMain(). Since UIApplicationMain() is documented to never return (like exit()), there is no point in having commands following it anyway. The pool would never get released.

Please fix the templates, or provide an FAQ or other documentation why this should be necessary on iOS (when it's clearly unneeded on Mac).