This is an old issue that I reported a few years ago. The application starts to consume a large amount of memory after a few days of operation. The problem persists even in the latest version 4.12.
The reported bug is quite complex and related to many parts of the app. In this case, this complex bug can’t be fixed at once. We’re working on this and trying to optimize Monosnap after every update.