Why does System.Threading.Timer stop on its own?

If you need a timer on a Windows Form then drop a System.Windows.Forms.Timer onto the form – there’s no reason to use a System.Threading.Timer unless you need better resolution than 55 ms.

The reason the timer “stops” is because it’s being garbage-collected. You’re allowing it to go out of scope in the Form1_Load method because you only declare it as a local variable. In order to keep the timer “alive”, it needs to be a private field on the form class so that the GC knows it’s still needed.

In other words:

public partial class Form1 : Form
{
    private System.Threading.Timer testTimer;

    ...

    public void Form1_Load(object sender, EventArgs e)
    {
        TimerCallback timerDelegate = new TimerCallback(tick);
        testTimer = new System.Threading.Timer(timerDelegate, null, 1000, 1000);
    }
}

But again, in this case it’s simplier to use System.Windows.Forms.Timer, which is an actual component in the toolbox that you can just drop onto the form.


Edit – As the comments now reveal, if this is just a test app and the real application is in a Windows Service, you cannot use System.Windows.Forms.Timer for that. Just remember not to let your System.Threading.Timer go out of scope.

Leave a Comment