On Tue, Mar 3, 2009 at 7:49 PM, Roland King wrote:
> You said "when I debug on the device one of my screens is getting memory
> warning". What is a 'memory warning', what is the text of the warning you
> are receiving, what does it say?
He is talking about UIKit (iPhone) which has things like the
I used this after opening sqlite:
// Modify cache size so we don't overload memory. 50 * 1.5kb
if (sqlite3_exec(database, "PRAGMA CACHE_SIZE=50;", NULL, NULL, NULL) !
= SQLITE_OK) {
NSAssert1(0, @"Error: failed to set cache size with message '%s'.",
sqlite3_errmsg(database));
}
Thanks
James
On Mar 3, 2009, at 10:27 PM, James Cicenia wrote:
self.spvc = [[StatePickViewController
alloc]initWithNibName:@"StatePicker" bundle:nil];
What type of property is spvc? Does it simply assign, or does it
retain its value? If the latter, you may end up with the object above
getting a retai
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)stateAc
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
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
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
You said "when I debug on the device one of my screens is getting memory
warning". What is a 'memory warning', what is the text of the warning
you are receiving, what does it say?
James Cicenia wrote:
hmmm,,,
how do I get that? I just put a nslog in there to see if in fact it
was memory.
hmmm,,,
how do I get that? I just put a nslog in there to see if in fact it
was memory.
james
On Mar 3, 2009, at 9:20 PM, Roland King wrote:
what is the memory warning?
James Cicenia wrote:
Hello -
I have dutifully tracked down every leak, except for that noted
nsindex issue that is
what is the memory warning?
James Cicenia wrote:
Hello -
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
Hello -
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.
I have dut
11 matches
Mail list logo
