In what area(s)?

/area runtime

What version of Dapr?

1.10.7

Expected Behavior

Actor timers should not put pressure on the Dapr sidecar.

Actual Behavior

The actor app's Dapr sidecar continuously grows in memory (see graph below at 23.5 GiB) until it is eventually killed. There is only one actor per app with a single timer however the RegisterTimerAsync method is called periodically with the same actor name in order to achieve the effect of a timer with a "floating window".

Steps to Reproduce the Problem

Instantiate an actor and then continuously call RegisterTimerAsync method with the actor name to watch how its memory behaves.

Release Note

RELEASE NOTE: FIX Runtime Memory leak with Actor reminders.