[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: deferred deallocation of local objects
From: |
Derek Zhou |
Subject: |
Re: deferred deallocation of local objects |
Date: |
Sat, 18 Oct 2003 12:20:20 -0700 |
User-agent: |
KMail/1.5.3 |
> However, there is another error condition possible between A and B
> without involving C:
>
> A vends O to B (oneway void) producing proxy P in B
> B uses P and releases it, sending release message to A
> A vends O to B again .... before receiving the release message.
> A receives the release message and destroys local proxy releasing O
> B receives reference to O from A and tries to use it ...
>
> Your solution would fix the original three-way problem, but not this
> two way problem.
Well, if A vends the object again, the retaincount at A should plus one; then
it takes 2 release messages from B to dealloc the object. IMHO, tracking
message sequence number in retain/release is overkill.
Derek
- Re: Fwd: deferred deallocation of local objects, (continued)
Re: deferred deallocation of local objects, Derek Zhou, 2003/10/16
Re: deferred deallocation of local objects,
Derek Zhou <=