I have found an iOS email app and everything is working well, except for a particular user account information Do look like an overreleased object.
The problem is that if I do not crash the NSZombies enabled (or use the device) this every time NSZombies are disabled, but when I want to see that the apple works as expected Is released.
So my question is, how can I track it down, if the zombie prevents it from being able to happen? Is the fact that the corpse is going on to prevent the accident, is it hanging up to keep an eye on the object?
So my question is, how can I track it if the lb is enabled Does it prevent it? Use
lower -autorelease s, if possible. / P>
You can consider Maulok stack logging to reduce the allocation, or callout.
Building a local autoridge pool can help you identify the realm.
Occasionally, Memory Scripting or Guard Mallok can help.
Simply running on a SIM / device can cause a difference - or even a separate device model.
By removing all other memory issues (like leaks, circular references) can also help you identify the issue.
You may also consider examining this address, in the event it is a tag indicator.
Even sending messages in more places can help reduce the S's face. [obj self] will be an error if obj is a zombie.
In addition, to stop the accident, is there really a corpse hanging in order to keep an eye on the object?
Yes the -dealloc of an object will be called as usual, but (normally) the memory used by the allocation will not be returned, and the example one Will become zombie - an example that generates runtime error if message is done.
Comments
Post a Comment