Where is the location to free shared resources?

Question

Hi everyone:
I have a shared instance of a class that stores several global objects. It is allocated like this:
+(SharedData*)sharedInstance
//RETURN: Pointer to this singleton class
static id sharedInstance = nil;
if(sharedInstance == nil)
sharedInstance = [[self alloc] init];
return sharedInstance;
My question is where are you supposed to release this shared instance?
PS. I tried doing it from applicationWillTerminate: after doing this:
UIApplication *app = [UIApplication sharedApplication];
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(applicationWillTerminate:) name:UIApplicationWillTerminateNotification object:app];
but it is never called.

Answer 1

Den B. wrote:
Loading images and sound takes all that time. I'm not that good yet at programming under iOS, so I don't know much about Core Data.
Core Data won't help much for images and sound, but how much of that do you have? Are you downloading it or is it in your app bundle? It shouldn't take that long. Plus, there may be some OS caching facilities you can take advantage of. Maybe consider loading images and sounds as you need them instead of all at once. Then there is nothing to worry about. Methods that don't exist are very easy to debug.
As for applicationWillTerminate: not being called, I put an NSLog statement in it to check. That's how I was able to find out. Are there any better ways to do it? (Because I'm not sure if a debugger break point would trigger in that situation.)
Are you sure you have connected an application delegate? Your previous post had a strange notification observer that didn't look right.
What do you mean by that? That it is not at all necessary to dealloc it since the app is terminating anyway and all of its memory will be released, right?
Yes, but I wouldn't put it like that. I once spend a long, long time debugging a program where the original author assumed the objects would be cleaned up at exist. He had not envisioned me using his module in another part of the code and then releasing it. It is always best to clean up.