From 56c5c18aac05e4ef68c99243696d0fcaacc1f0c8 Mon Sep 17 00:00:00 2001 From: baldurk Date: Tue, 26 Jan 2021 11:28:36 +0000 Subject: [PATCH] Tweak leak threshold on vulkan test * It seems like some drivers don't free some memory from the resident set until a certain point, meaning the peak memory is higher after a couple of captures then goes down. This isn't a true leak and us checking the entire process's working set size is a very poor litmus test, so bumping this value is fine. --- util/test/demos/vk/vk_leak_check.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/util/test/demos/vk/vk_leak_check.cpp b/util/test/demos/vk/vk_leak_check.cpp index c449e438a..1ec3554f6 100644 --- a/util/test/demos/vk/vk_leak_check.cpp +++ b/util/test/demos/vk/vk_leak_check.cpp @@ -69,8 +69,8 @@ RD_TEST(VK_Leak_Check, VulkanGraphicsTest) while(Running()) { - // allow a generous 500MB, we're really only after catching big leaks here - if(GetMemoryUsage() > 500 * 1000 * 1000) + // allow a generous 750MB, we're really only after catching big leaks here + if(GetMemoryUsage() > 750 * 1000 * 1000) { TEST_ERROR("Memory usage of %llu is too high!", GetMemoryUsage()); break;