Search NSZombie in Google. It may be what you need.
Le 6 mai 09 à 01:04, Malayil George a écrit :
I don't think I have a leak...quite the opposite. I think the sample
app I'm
playing with is crashing because I might be releasing an object too
soon.
Which is why I resorted to retainCounts to try and track it down...
George
On Tue, May 5, 2009 at 7:01 PM, Nick Zitzmann <n...@chronosnet.com>
wrote:
On May 5, 2009, at 4:54 PM, Malayil George wrote:
If the getter is always incrementing the reference count by 1, I
would
expect the reference count at each NSLog, where I am using the
getter, to
be
2 above the previous value. This doesn't seem to be the case for
line 3 of
the output where it has gone up by only 1. In subsequent NSLog()
statements
it seems to go up by 2.
This behavior is seen again after the drain. Am I missing something?
Yes - don't worry about retain counts unless Instruments or the
leaks tool
is telling you that you have a memory leak. Do you know for a fact
that you
have a memory leak?
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/devlists%40shadowlab.org
This email sent to devli...@shadowlab.org
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
