Home/ Questions/Q 200177
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T17:05:20+00:00

In this question @Jon skeet referenced this old blog post by the authority Chris

  • 0

In this question @Jon skeet referenced this old blog post by the authority Chris Brumme.

I was wondering, do I need to follow all calls to GC.SuppressFinalize(this) with a GC.KeepAlive(this) to avoid weird race conditions where a finalizer can be invoked during the time a disposer is running in heavily multithreaded applications?

If so, can you come up with a sample program that exposes this bug?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No. GC.KeepAlive doesn’t actually do anything; its purpose is to ‘fool’ the runtime into preventing a specific object from being garbage collected between the start of the method and the call to GC.KeepAlive.

    Any method call will keep an object alive in this way: you could pass it to Console.WriteLine, call ToString, or even… GC.SuppressFinalize.

    (Or as MSDN puts it:

    The KeepAlive method performs no operation and produces no side effects other than extending the lifetime of the object passed in as a parameter.)

    • 0