Hello Again!
Apart from a few small things to be implemented my little app is approaching 1.0 release status. I'm trying to ensure that I've not made any nasty errors that will result in excess memory or CPU usage so I'm running in the simulator attached to Instruments using the leaks template. It seems pretty good: I'm not leaking much memory and once initialised memory usage is relatively static. But I have one annoying leak:
Every time I call setItems:animated: on a UIToolbar I leak 32 bytes. The leak appears to be inside Apple's code somewhere. Does anyone else get this? I would note that this only happens if I pass YES for animated:.
Code I am using is
and
Any ideas? Am I doing something that is obviously wrong?
Apart from a few small things to be implemented my little app is approaching 1.0 release status. I'm trying to ensure that I've not made any nasty errors that will result in excess memory or CPU usage so I'm running in the simulator attached to Instruments using the leaks template. It seems pretty good: I'm not leaking much memory and once initialised memory usage is relatively static. But I have one annoying leak:
Every time I call setItems:animated: on a UIToolbar I leak 32 bytes. The leak appears to be inside Apple's code somewhere. Does anyone else get this? I would note that this only happens if I pass YES for animated:.
Code I am using is
Code:
[statusView setItems:[NSArray arrayWithObjects:statusTextItem,downloadingProgressItem,flexiOne,refreshItem, nil] animated:YES];and
Code:
[statusView setItems:[NSArray arrayWithObjects:statusTextItem,downloadingProgressItem,flexiOne,cancelItem, nil] animated:YES];Any ideas? Am I doing something that is obviously wrong?