Am 14.03.2012 17:57, schrieb Warp:

>>>     And btw, cyclic references are not the only problematic situation with
>>> reference counting. There are cases where objects may be deleted too early,
>>> while there's still code using them.
>
>> I can't think of any reason why that could possibly happen, provided
>> that the reference counting is implemented in a thread-safe manner.
>
>    Module A has a reference-counting smart pointer pointing to an object B.
>
>    A member function of that object B calls a function of module A. Said
> function of A drops the reference to object B. Since it was the only
> reference pointing to it, the object B gets deleted. When the function
> in A ends, the execution returns to the member function of B, which now
> operates on a deleted object. Undefined behavior ensues.
>
>    Yes, that *can* happen.

Hm... you do have a point there.

Post a reply to this message