Weak references don&#x27;t have to be very slow. You need to track all weak references to any given object, but that&#x27;s no big deal. When it comes to actually zeroing out the weak references on deallocation, it depends on how you do it.<p>With an eager implementation, you need to ensure that deallocation and zeroing is atomic. The entire operation of decrement refcount -&gt; deallocate -&gt; zero weak references can&#x27;t be interrupted by looking up a weak reference. In a multithreaded environment that means there&#x27;s locking needed.<p>However, you can do a lazy implementation which doesn&#x27;t suffer so much. Here, you keep a separate weak reference count in the object itself. When the normal reference count reaches zero, you deinitialize the object (decrement the refcount of anything it refers to, run custom deinitialization code if any), but leave the memory for the object itself intact. Then, upon accessing a weak reference, you can just check to see if the target is in this &quot;zombie&quot; state, and zero out the weak reference at that point. Once the weak reference count also reaches zero, the object memory can be deallocated.<p>Objective-C uses the eager approach for weak references, which is necessary because of compatibility concerns. Swift uses the lazy approach with native Swift objects, although it still has to use the eager approach for subclasses of Objective-C classes.