Blazor Server Side Timer is running amok

Question

I have this ServerSide Blazor running and I have:

listTimer = new System.Timers.Timer();
        listTimer.Interval = 1000;
        listTimer.Elapsed += async (s, e) =>
        {
            await Utils.LogToConsole(jsRuntime, DateTime.Now.ToString());
        }

    `

But when I run this I get huge amounts of log in the Chrome console but I expect to see only logs each 1000 millis. Anyone seen this problem and found a workaround. Yes I could check the actual time and compare but I dont like it triggering like thats crazy.

I have 3.1.300 preview015048 – Martin Michaelsen Jun 22 '20 at 11:07 — Martin Michaelsen, Jun 22 '20 at 11:07

boindiil · Answer 1 · 2020-06-22T19:21:56.397

5

You habe to unsubscribe the timer-Event when disposing the component. The easiest way to do that ist disposing the timer itself.

@using System
@implements IDisposable

@code {
    public void Dispose()
    {
        listTimer?.Dispose();
    }
}

edited Jun 22 '20 at 19:21

answered Jun 22 '20 at 11:11

boindiil

5,805
1
28
31

1

@PeterMorris thanks for your comment, your solution is nicer. I have updated my answer. – boindiil Jun 22 '20 at 19:22

H H · Accepted Answer · 2021-09-05T06:09:54.260

2

... I get huge amounts of log in the Chrome console

That can only happen when you create and assign the Timer more than once.

You didn't post that code but I guess you need something like:

if (listTimer == null)
{
    listTimer = new System.Timers.Timer();
    listTimer.Interval = 1000;
    listTimer.Elapsed += async (s, e) =>
    {
        await Utils.LogToConsole(jsRuntime, DateTime.Now.ToString());
    }
}

and a Timer is IDisposable , so add:

@implements IDisposable

and this to @code:

public void Dispose()
{
    listTimer?.Dispose();
}

edited Sep 05 '21 at 06:09

answered Jun 22 '20 at 12:22

H H

263,252
30
330
514

Thanks very much. I've done more Blazor WASM but now I understand more of the nature of Blazor Server:-) – Martin Michaelsen Jun 23 '20 at 07:08
1

You must dispose the timer too, or it will hang around forever – Peter Morris Jun 23 '20 at 07:35

score 0 · Answer 3 · answered Nov 18 '22 at 17:40

0

The exact same hapens to me, but it doesn't seem like Dispose() is being called at all.

answered Nov 18 '22 at 17:40

Tiago Alves

27
1
10

Blazor Server Side Timer is running amok

3 Answers3

Linked