I am still unable to resolve the issue with memory leaks after calls the Writeablebitmap filter extensions. The leaks may not be in the extensions, but they make the extensions unusable.
As an aside... I was able to make significant performance improvements in every filter by using Parallel.For loops for processing. For example, I was able to reduce the time for a 3x3 Gaussian blur from 2.45 seconds to 0.67 seconds by making this simple change. My platform was a WPF desktop app.
The filter extensions all return a new WriteableBitmap. I will be trying a different approach that updates the Back Buffer of the original bitmap instead. Hopefully this will work around the leaking objects!
In the mean time, if anyone has any guidance I would be interested to hear it. That is if anyone actually reads this note (this project does not seem to be very active!)
As an aside... I was able to make significant performance improvements in every filter by using Parallel.For loops for processing. For example, I was able to reduce the time for a 3x3 Gaussian blur from 2.45 seconds to 0.67 seconds by making this simple change. My platform was a WPF desktop app.
The filter extensions all return a new WriteableBitmap. I will be trying a different approach that updates the Back Buffer of the original bitmap instead. Hopefully this will work around the leaking objects!
In the mean time, if anyone has any guidance I would be interested to hear it. That is if anyone actually reads this note (this project does not seem to be very active!)