08-28-2019, 11:46 PM
Was it a true leak or just high memory usage? Was it a debug build or release? Could be they have some new debugging features that use a lot of memory, that has already happened once and was the reason we pretty much got rid of a memory leak finder library.