Re: memory management issue?
Re: memory management issue?
- Subject: Re: memory management issue?
- From: Steven Crosley <email@hidden>
- Date: Fri, 1 Feb 2008 11:36:33 -0600
Hey Adhamh,
I did try releasing it at the end of the function, but same result. I
haven't looked at NSZombiesEnabled, I'll try that. Thanks for the
quick response.
Steven
On Feb 1, 2008, at 11:25 AM, Adhamh Findlay wrote:
On Feb 1, 2008, at 11:13 AM, Steven Crosley wrote:
Hi,
I'm still pretty new to Cocoa and have just learned the hard way
about memory management. My app keeps dying in the function
below. I've gone back and cleaned up my classes according to the
Memory Management Rules (http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html#/
/apple_ref/doc/uid/20000994), but it doesn't seem to help. The
first and second time that this function gets accessed it works, no
problem. The third time it gets called it dies at:
array = [moc executeFetchRequest:request error:&error];
I put a breakpoint in right before it, and all the variables appear
to be in line. I've been stuck on it for a couple weeks now, so if
anyone has any suggestion of how I can better debug it, I'd really
appreciate it.
The error message that I get is: Program received signal:
“EXC_BAD_ACCESS”.
Have you tired releasing the fetch request at the end of the
function instead of autoreleaseing it?
Have you tired using NSZombiesEnabled? http://www.cocoadev.com/index.pl?NSZombieEnabled
Adhamh_______________________________________________
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
_______________________________________________
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