An empty finalizer (which negates the effect of the superclass finalizer).
A finalizer can use this method to resurrect itself or an object that it references.
A finalizer is an appropriate vehicle for performing this task, assuming the native peer holds no critical resources.
The disadvantage of this approach is that the existence of the finalizer means that the object is kept alive longer than it otherwise would be.
NET Framework 4, by default, if a Task that has an unobserved exception is garbage collected, the finalizer throws an exception and terminates the process.
For example, depending on a finalizer to release a persistent lock on a Shared resource such as a database is a good way to bring your entire distributed system to a grinding halt.
