Hi Miles-
This may not be your issue, but I know it has bitten me a few times...
a common tool in tracking down over-released memory is to set
NSZombieEnabled. I sometimes end up setting this in the early, crashy
stages of my development and then forget to disable this in the later,
perf
On May 1, 2009, at 8:32 AM, Miles wrote:
For example, I have created a new project where the delegate creates
and
immediately releases a view controller that doesn't have anything in
it at
all. Object alloc still shows a handful of objects as created and
still
living, such as:
#Object
Hi guys-
I'm still really struggling with this. I keep creating the most simple
examples I can and ObjectAlloc continues to show objects as 'created and
still living' when they really shouldn't be. At this point I would probably
just assume it's a bug in ObjectAlloc or elsewhere but over time my a
Wow. In that particular example it was '[UIScreen mainScreen]
applicationFrame' that was causing the problem. When I changed that to a
CGRectMake, the view was not longer living once I released it. Does
'[UIScreen mainScreen] applicationFrame' cause some sort of caching issue?
Now I'm at a point w
I've narrowed this down to the smallest case I can.
I have a method that loads a view and immediately releases it:
UIWindow *win= [UIApplication
sharedApplication].keyWindow;
TestVC *test = [[TestVC alloc] init];
[win addSubview:test.view];
[test.view removeFro
Very interesting, I'll give all that a shot and report back. Thanks so
much!
On Apr 24, 2009, at 7:07 PM, Peter N Lewis
wrote:
On 25/04/2009, at 8:28 , Miles wrote:
I just mean that I'm adding some labels and images to the view. I
have
quadruple checked that they are all being releas
On 25/04/2009, at 8:28 , Miles wrote:
I just mean that I'm adding some labels and images to the view. I have
quadruple checked that they are all being released, but I must be
overlooking something.
I doubt its your issue, but I recently had a problem like this that
took me far too long to tra
I just mean that I'm adding some labels and images to the view. I have
quadruple checked that they are all being released, but I must be
overlooking something.
For example, ObjectAlloc points to the second line here, where I declare
UIImage *logo as being created and still living, even though it's
Am 24.04.2009 um 01:27 schrieb Miles:
But when I run this in ObjectAlloc, a bunch of parts of the view are
still
showing as 'created and still living'. It's very odd considering the
deallocs are both called so nothing should be hanging around.
What is „a bunch of parts of the view“ in your
I don't have an answer for you, but I'd like to mention that I've also
experienced some strange issues with the ObjectAlloc tool. Last night
I was seeing an NSWindow that was released to the point that it would
have a retain count of -10 and I'm not sure how thats possible. It
seems, to me at least
OK, thanks. I got that one figured out.
Now I'm seeing another issue that may be related where I show a UIView by
instantiating the view controller:
statsViewController= [[StatsViewController alloc] init];
statsViewController.view.alpha= 0;
[win addSubview:statsViewController.
On 23/04/2009, at 10:19 , Miles wrote:
I have a timer that continues calling a method that for the moment
(testing
purposes) only contains:
NSArray *tmp = [NSArray arrayWithArray:animatingTilesArray];
The time is setup like this:
animationTimer= [NSTimer scheduledTimerWithTimeInterval:0.5
I have a timer that continues calling a method that for the moment (testing
purposes) only contains:
NSArray *tmp = [NSArray arrayWithArray:animatingTilesArray];
The time is setup like this:
animationTimer= [NSTimer scheduledTimerWithTimeInterval:0.5 target:self
selector:@selector(doAnimation:
13 matches
Mail list logo
