Practicality of memory debugging idea?
Practicality of memory debugging idea?
- Subject: Practicality of memory debugging idea?
- From: Graham Cox <email@hidden>
- Date: Mon, 14 Dec 2009 22:48:15 +1100
Hi all, just throwing this one out there, see if it's worth anything.
I'm having a problem tracking down a very elusive memory management bug. It's a simple over-release, somewhere, but extremely rarely. The problem is that the only reports I've had of it so far are field reports indicating a crash on -release sent to a freed object from the cyclic autorelease pool drain. That means all trace of what the object was or where it came from has gone.
I'm wondering if there's any way I can do something like checking in -dealloc if my object is sitting in an autorelease pool anywhere, and if so flag that as a over-release-bug-yet-to-come. If feasible, I'm also wondering whether it would be worth suggesting this to Apple as a useful debugging flag that could be built-in at a low level like zombies are.
Thoughts?
--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