Re: Garbage collection problem

FROM : Dent John
DATE : Wed Jan 09 14:24:01 2008

Hi Jonathon,

So, thanks for the quick response there.

The object in question is instantiated in my NIB and, though is not 
visible, it has outlets to other objects (specifically an array 
controller and a spinning circle thing). I figured that would be 
strong enough to prevent collection.

Also, the self is obviously stored in SyncServices as it knows that 
it's a callback-able class for when of tries to 
client:mightWantToSyncEntityNames:.

I implemented the finalize method just now and, sure enough, the 
object is getting collected.

I'll try making the object pop itself into a global to see if it helps.

d.
--
Sent from my iPhone

On 9 Jan 2008, at 11:57, Jonathon Mah <<email_removed>> wrote:

> Hi,
>
> On 2008-01-09, at 21:15, Dent John wrote:
>

>> For example, in a classes init method, I get it to NSLog the self 
>> pointer. Then, after some time, I see errors relating to the class.

>
>
> Are you storing a reference to that instance in a "strong" location, 
> such as a global variable? Otherwise the garbage collector has no 
> idea that it might be used later on.
>
>
>
> Jonathon Mah
> <email_removed>
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>