This is a known issue with no easy solution. EventArgs in WPF are classes allocated from the heap. We need to pool these objects.

Good to know! These are the only per-frame allocations that I have. I imagine this is a difficult fix?

These specific cases can probably be easily optimized. I will find time to analyze this and I will let you know

Thank you. I am happy to test to see if the behavior is resolved

Hello! In 3.2.4, I'm seeing significant per-frame allocations 1.7kb per frame, which is 1MB every ~10 seconds. It is coming from EventHandlerStore.RaiseEvent() (screenshot).

image.png (172,960 bytes)   

image.png (172,960 bytes)   

Hello,

We found the source of the issue, the UpdateLayout event raised by the BackgroundEffectBehavior, and it turns out to be very easy to fix for your case scenario.

You can go to the EventArgs.cs code and change the InvokeHandler method for this code:

  internal static void InvokeHandler(Delegate handler, IntPtr sender, IntPtr args) {
    EventHandler handler_ = (EventHandler)handler;
    if (handler_ != null) {
      handler_(Extend.GetProxy(sender, false), EventArgs.Empty);
    }
  }

There is another allocation during the RaiseEvent related to a string being passed from the native library that I also fixed, but that requires changes in the native library too. You'll get them in the upcoming 3.2.8 version we're going to release very soon.