Everyone is told to not use **DynamicResource** during its childhood in WPF-(wonder)land. They are simply evil and they kill the app performance. Sometimes, we fall in the dark side of the force and use them effectively to be sure that the application will follow the trend and suits itself well. This is not as bad as it seems and it is in fact sometimes necessary and wanted. But today, while I was trying to improve the performance and the memory usage of a WPF application I work on, **I discovered that they were also creating memory leaks!** I felt betrayed. I was using them and they put a knife in my back while I trusted them to be useful. In this post we will see how it can happens, and how to solve this (little) issue. I was not alone in this situation and I found out that there were both a work-around and an hotfix available. Here is the information I gathered.