Nick,
Thanks, I suspected as much.
Bob
On Sep 29, 2009, at 3:27 PM, Nick Zitzmann wrote:
On Sep 29, 2009, at 4:18 PM, Bob Barnes wrote:
I wanted to follow up my email from last week with some additional
questions about the leaks instrument and what it is or isn't trying
to tell me. W
On Sep 29, 2009, at 4:18 PM, Bob Barnes wrote:
I wanted to follow up my email from last week with some additional
questions about the leaks instrument and what it is or isn't trying
to tell me. When running the leaks instrument with NSZombieEnabled
several lines of the following code are f
On Sep 25, 2009, at 5:46 PM, Bob Barnes wrote:
Kyle/Nick/Greg,
Thank you guys. Took a little digging but the combination of
NSZombie & instruments object allocation did the job. After years
working with Java I find myself tripping over memory management
issues much too often. I had all
On 26/09/2009, at 9:46 AM, Bob Barnes wrote:
I'm concluding (perhaps incorrectly) that using buttonWithType:
doesn't grant 'object ownership' in the same way that alloc does.
I'd say that was true, since 'buttonWithType:' doesn't contain the
words 'new', 'alloc', 'create', 'retain' or '
Kyle/Nick/Greg,
Thank you guys. Took a little digging but the combination of
NSZombie & instruments object allocation did the job. After years
working with Java I find myself tripping over memory management issues
much too often. I had allocated a UIButton using buttonWithType: and
th
On Sep 25, 2009, at 12:14 PM, Bob Barnes wrote:
If I'm reading this correctly, not a given by any means, Core
Foundation is trying to get the retain count for an object, possibly
a CALayer, where the reference pointer is no longer valid, but how
do I determine what object? I've tried runnin
On Sep 25, 2009, at 1:14 PM, Bob Barnes wrote:
If I'm reading this correctly, not a given by any means, Core
Foundation is trying to get the retain count for an object, possibly
a CALayer, where the reference pointer is no longer valid, but how
do I determine what object?
Use Instruments
