Question

While looking at the Timer documentation I ran across the following example with this comment:

    // Normally, the timer is declared at the class level,
    // so that it stays in scope as long as it is needed.
    // If the timer is declared in a long-running method,  
    // KeepAlive must be used to prevent the JIT compiler 
    // from allowing aggressive garbage collection to occur 
    // before the method ends. You can experiment with this
    // by commenting out the class-level declaration and 
    // uncommenting the declaration below; then uncomment
    // the GC.KeepAlive(aTimer) at the end of the method.
    //System.Timers.Timer aTimer;
    code in between
    // If the timer is declared in a long-running method, use
    // KeepAlive to prevent garbage collection from occurring
    // before the method ends.
    //GC.KeepAlive(aTimer);

Does this mean that the GC in C# is allowed to garbage collect local variables even if it would have side effects? Presumably because I’m not accessing the timer afterwards again the GC can collect it earlier?

Not sure I’m a fan of such an optimization if I understand this correctly (but then I probably don’t 😉 )

Answer 1

Yes, GC might collect local variable before ending of the scope, as soon as after last use of the variable. Putting GC.KeepAlive at the end of the method ensures that the variable will be ‘alive’ until the KeepAlive call.

C# is imperative language so the GC hasn’t been designed to know anything about side effects.