Forum

[sal_park]

Originally Posted by JonnyThunder

Yes, if you alloc an object you are responsible for releasing it. Are you sure it's this which is being deallocated, and not something within this class?

Hi Jonny,

spot on advice - the object being created here:

self.myUploadRootViewController = 
   [[uploadRootViewController alloc  ] 
       initWithNibName:@"uploadRootViewController" bundle:nil];
   NSLog(@"hash is [%i]",[myUploadRootViewController hash]);

Is not that same object instance that is being destroyed here:

- (void)dealloc {
	NSLog(@"****** uploadRootViewController being dealloced");
	NSLog(@"hash is [%i]",[self hash]);
    [super dealloc];
}

So given I've only created 1 object, where is the other instance coming from ? is it being created from the info in the nib ?

thanks

sal