In managed languages with garbage collection, when are finalizers typically executed?

In managed languages with garbage collection, when are finalizers typically executed?

• A. Finalizers run at deterministic times when dispose is called.
• B. Finalizers run only when the program exits.
• C. Finalizers run at unpredictable times during garbage collection cycles.
• D. Finalizers never run.

Answer: (C)

Finalization timing is non-deterministic in garbage-collected environments. When an object becomes eligible for collection, the runtime may place it in a finalization queue and run its finalizer later, typically on a separate finalizer thread during a garbage-collection cycle. The exact moment is governed by memory pressure and the runtime’s scheduling, so you can’t predict when it will happen. This is why finalizers aren’t tied to explicit dispose calls and aren’t guaranteed to run at program exit or in any specific order. In short, finalizers are executed during garbage collection cycles, at unpredictable times.

Finalization timing is non-deterministic in garbage-collected environments. When an object becomes eligible for collection, the runtime may place it in a finalization queue and run its finalizer later, typically on a separate finalizer thread during a garbage-collection cycle. The exact moment is governed by memory pressure and the runtime’s scheduling, so you can’t predict when it will happen. This is why finalizers aren’t tied to explicit dispose calls and aren’t guaranteed to run at program exit or in any specific order.

In short, finalizers are executed during garbage collection cycles, at unpredictable times.