Weird behaviour with retainCount

跟風遠走 提交于 2019-11-29 15:33:09
David Schaefgen

You should never use -retainCount, because it never tells you anything useful. The implementation of the Foundation and AppKit/UIKit frameworks is opaque; you don't know what's being retained, why it's being retained, who's retaining it, when it was retained, and so on.

Also see: StackOverflow | when to use retainCount for an excellent recount of why you don't use retainCount.

And to echo Dave DeLong: Please everyone go to http://bugreport.apple.com and request that -retainCount be deprecated. The more people that ask for it, the better.

nothing wrong with 2147483647

2147483647 is INT_MAX. And INT_MAX is the retaincount for string literals (ie @"foo" strings defined in your code). This means they will never be released.

btw, don't use retainCount.

retainCount returns NSUInteger and you should print it in this way ...

NSLog( @"%lu", (unsigned long)[blabla retainCount] );

%d is used for signed 32-bit integer (int). NSUInteger is on 32-bit platform defined as unsigned int and on 64-bit platform as unsigned long. Upper example is safe for both 32/64-bit platforms.

What is the wrong with the code??

You are calling retainCount.

retainCount is next to useless for debugging and should never, ever, be used in production code. The retain count of an object is an internal implementation detail that will often be of a value that is unfathomable.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!