Re: runtime error (-> ObjectAlloc)
Re: runtime error (-> ObjectAlloc)
- Subject: Re: runtime error (-> ObjectAlloc)
- From: Daniel Child <email@hidden>
- Date: Thu, 13 Mar 2008 11:44:39 -0400
An autorelease pool got me through the parsing operation without
issue. Thanks for your input.
In ObjectAlloc, is there a way to figure out what exactly how each
"General Block" matches up with objects in code? I can make rough
guesses based on the data types and their behavior, but can the
correlation be found precisely?
On Mar 12, 2008, at 1:47 PM, Nick Zitzmann wrote:
If you're using Tiger, then you'd use ObjectAlloc to keep track of
objects created by your app, and MallocDebug to look for leaks. And
I hope you have plenty of RAM on hand, since ObjectAlloc will
devour it all...
Anyway, you want to look for hills and plateaus in object creation,
e.g. lots of objects that get created at once, and then released
all at once.
_______________________________________________
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