Object resurrection

<p>In <a href="/facts/Object-oriented_programming_languages/TxNMEcao">object-oriented programming languages</a> with <a href="/facts/Garbage_collection_(computer_science)/j2vlIu7g">garbage collection</a>, object resurrection occurs when an <a href="/facts/Object_(computer_science)/eX99dtAw">object</a> becomes reachable (in other words, no longer garbage) during the process of <a href="/facts/Object_destruction/QgCnhNlf">object destruction</a>, as a side effect of a <a href="/facts/Finalizer/6vU0SvEb">finalizer</a> being executed.
</p><p>Object resurrection causes a number of problems, particularly that the possibility of object resurrection – even if it does not occur – makes garbage collection significantly more complicated and slower, and is a major reason that finalizers are discouraged. Languages deal with object resurrection in various ways. In rare circumstances, object resurrection is used to implement certain design patterns, notably an <a href="/facts/Object_pool/bjCz67kC">object pool</a>, while in other circumstances resurrection is an undesired bug caused by an error in finalizers, and in general resurrection is discouraged.
</p>

Object resurrection open-in-new

Object resurrection