Re: Solved? Cocoa/Java - NSCoding woes...
Re: Solved? Cocoa/Java - NSCoding woes...
- Subject: Re: Solved? Cocoa/Java - NSCoding woes...
- From: Aram Greenman <email@hidden>
- Date: Sat, 1 Mar 2003 01:48:24 -0800
On Friday, February 28, 2003, at 09:29 PM, janderson wrote:
My code, which is pure Cocoa, was crashing at the end of my GUI "event
loop" which unarchived a custom class object (reporting error signal
10 or 11).
I know that the default application autorelease pool is flushed at the
end of this "event loop."
Although my code makes no to attempt access the unarchived object when
it crashes, (I even called release on the unarchived object within the
loop),
Don't release an object that you didn't create with +alloc or -copy or
a variant thereof, unless you have retained it. All other methods which
return an object return an autoreleased object. The signal occurs when
the pending autorelease is sent to an object which no longer exists
because you already released it.
Aram
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.