Possible bug with FreeBrush()
Posted: Mon Jul 18, 2022 12:24 pm
Hello,
I'm working on a configurable clock with newsfeed and other features, for this project I'm trying to use RebeSDL but I've noticed that memory is not released after any FreeBrush() call for hardware brushes, while software ones have not this problem.
I free all brushes when a new clock layout is selected but memory keep increasing, btw the resource monitor show the right number of loaded brushes after the FreeBrush() commands.
I'm on Windows 10
I'm working on a configurable clock with newsfeed and other features, for this project I'm trying to use RebeSDL but I've noticed that memory is not released after any FreeBrush() call for hardware brushes, while software ones have not this problem.
I free all brushes when a new clock layout is selected but memory keep increasing, btw the resource monitor show the right number of loaded brushes after the FreeBrush() commands.
I'm on Windows 10