Re: All my leaks are gone... but now a memory warning?!
Re: All my leaks are gone... but now a memory warning?!
- Subject: Re: All my leaks are gone... but now a memory warning?!
- From: James Cicenia <email@hidden>
- Date: Tue, 3 Mar 2009 22:27:18 -0600
I see that on that one screen it does chew up memory after I select
and process. My other three screens all behave very nicely.
So, maybe it is the way I have architected this screen:
When I load the view it seems ok.
Then I popup a little view for the user to select a state:
- (void)stateAction:(id)sender{
self.spvc = [[StatePickViewController
alloc]initWithNibName:@"StatePicker" bundle:nil];
spvc.view.frame = CGRectMake(28,65,260,258);
[spvc setMyParentController:self];
[spvc setDialogView:fruitTypeView];
[spvc viewWillAppear:TRUE];
[fruitTypeView addSubview:spvc.view];
}
Then when they click the state from that view:
-(void)resetState{
[spvc.view removeFromSuperview];
[spvc release];
[self viewWillAppear:TRUE]; <<<<<===== IS THIS THE CULPRIT?
}
Do I need to release something?
Thanks
James
On Mar 3, 2009, at 10:12 PM, Roland King wrote:
well how much memory is your app using? One of the performance tools
should be able to help you not just get rid of leaks, but tell you
how big your memory footprint is. Just because you're not leaking
objects doesn't mean you're not pooling them up somewhere on an
autorelease pool. If you use instruments or object alloc etc do you
see a rapidly climbing memory usage or huge numbers of allocated but
not yet freed objects? Are you making objects which uses masses of
memory?
The performance tools should be able to run against the simulator
and show how your memory footprint is changing.
James Cicenia wrote:
Ok -
How do I get more information? Or what kind of information do you
need?
The memory issue is very opaque to me. It just happens.
Is there anyway to get more info?
Thanks
James Cicenia
On Mar 3, 2009, at 9:52 PM, David Duncan wrote:
On Mar 3, 2009, at 7:16 PM, James Cicenia wrote:
I have dutifully tracked down every leak, except for that noted
nsindex issue that is a red-herring. Otherwise I get none now
with my instruments. However, when I debug on the device one of
my screens is getting memory warning and after a few clicks
freezes up my phone.
Memory warnings are a fact of life on iPhone OS, but without more
information on why your freezing, it will be nearly impossible to
actually help.
--
David Duncan
Apple DTS Animation and Printing
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden