Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FluidMoveBehavior memory leak

See original GitHub issue

As described in https://social.msdn.microsoft.com/Forums/lync/en-US/f14d1486-24ba-447b-9712-e16f5457a08b/fluidmovebehavior-memory-leak-bug there is a memory leak with the static TagDictionary.

I write this as a reminder/question, as I think this issue is still existing in the current code base.

Issue Analytics

State:
Created 4 years ago
Comments:9

Top GitHub Comments

1reaction

tibelcommented, Apr 14, 2023

I’ve moved on as I haven’t done WPF development in the last few years.

0reactions

brianlagunascommented, Apr 11, 2023

Hey @tibel was there a specific reason you closed your PR? Did you determine that your approach does not solve the problem?

Top Results From Across the Web

FluidMoveBehavior Bug (& Memory Leak!) - Ratish Philip's Blog

So I thought of a different workaround using Reflection. In the UserControl.Unloaded event handler: 1. Get access to the TagDictionary field in ...

Preventing Memory Leaks with Attached Behaviours

So I find the choice of words to be correct, you are leaking memory to objects you no longer use. You expect the...

Using Fluid Move Behavior with listbox | XAML TAG

Yes, there does appear to be a memory leak in FluidMoveBehavior. My profiler showed some strange happenings, and a quick google shows i'm...

Fighting Common WPF Memory Leaks with dotMemory

We can drill down and look at the Key Retention Paths to see WPF is retaining our object in memory.

Use Visual Studio Performance Profiler for ...

NET profiling tools can be used to analyze OpenSilver application performance including CPU usage, Memory Usage and other available analysis Visual Studio ...