Re: if statement causing 32 Byte leak?
Re: if statement causing 32 Byte leak?
- Subject: Re: if statement causing 32 Byte leak?
- From: Graham Cox <email@hidden>
- Date: Mon, 11 Jan 2010 12:17:43 +1100
On 11/01/2010, at 11:01 AM, Paul Sanders wrote:
> Have
> you got the energy to file an enhancement request Graham?
Filed: #7528006
"It would be useful to have available the following two debugging functions:
a) A way to test whether a given object is referenced by any current autorelease pool.
b) A way to dump (log) the content of all current autorelease pools.
One problem with debugging over-release issues is when an object is deallocated but a reference to it remains in an autorelease pool. The later pop of the pool will crash, but information about what object caused the problem is lost unless zombies is on, and even then that tells you very little about where the real problem lies, the answer to which will often be found in the calling stack for the prior release that called -dealloc.
The ability to assert on an autorelease pool holding a reference to self at -dealloc time would be a useful weapon in the fight against this sort of bug, without the overhead of running Instruments which is often overkill for this sort of problem, as well as causing performance issues that discourage its use. "
Please file dupes to help get it noticed, if you think this would be useful.
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden