brunoherbelin
commented
3 years ago Thanks for pointing this out. There were indeed new memory leaks since the last time I checked!
But a thourough memory check and cleanup should now have cleared the issue.
Below an example with Valgrind memory consumption test during loading & closing sessions mutiple times.
Detailed legend: 4 times cycle of loading a small session and closing it, then load a larger session 1 time, close it, and load again the small session 1 time before terminate the program. You can note the bouncing up-down every time the session is closed: this is because vimix first creates the new session before doing the transition with the closing session (at one point, two sessions are therefore in memory)
Please note however that (mostly under Linux), memory management is not strict and the system keeps a reserve of memory for future use: the idea is that an application that once needed a certain amount of space will very probably need it again later. Thus the return to baseline is not a return to zero.
OlegoroV
Memory usage gets higher on every new video source opening (even before I press Create button), reloading session, opening new session, fading video in (although memory was already eaten a little bit by creating this source). Fading video out doesn't decreases memory usage.