Hello,
In general, the retain count is entirely meaningless. The retain
count of any given object, especially objects that were created by
or have passed through the Apple provided frameworks, may be
seemingly random due to the internal implementation details of the
class or of the frameworks. Caching, singletons, and any of a
number of optimizations could impact the retain count.
Frankly, -retainCount should be deprecated and eliminated.
If you are trying to find a leak, then use one of the tools on the
system designed for exactly that -- leaks, Object Graph in
Instruments for GC, Object Alloc for non-GC, etc...
In my special case (the memory leak in the CocoaEcho sample) I used
Instruments with the "leaks" instrument and it shows up several memory
leaks. They seem to come from the openstream: and closestream: methods.
Is the retain in these methods right after I got the streams with -
getInputStream:outputStream: or is it wrong? How can I test it to go
sure?
I'm not really sure about this.
Thanks for your help
Jens
_______________________________________________
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 [EMAIL PROTECTED]
