From 09c042f994c2fe29c7c32fb7cfda690c48b86a83 Mon Sep 17 00:00:00 2001 From: Dennis Brakhane Date: Fri, 17 Jan 2025 07:36:04 +0100 Subject: [PATCH] increase timeout waiting for entriesLock (#1026) Turns out 33ms aren't "more than enough", during shader compilation the timeout was often reached. Increasing it to 100ms seems to solve the issue, and it's still short enough to avoid blocking the application for too long in case something goes wrong. --- WickedEngine/wiBacklog.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/WickedEngine/wiBacklog.cpp b/WickedEngine/wiBacklog.cpp index ed3ecf240..98ad2c8f8 100644 --- a/WickedEngine/wiBacklog.cpp +++ b/WickedEngine/wiBacklog.cpp @@ -390,9 +390,8 @@ namespace wi::backlog // It won't appear in the logfile or backlog, but will still be written to the debug output. // // The time to wait is kinda arbitrary, but it shouldn't be too short, as the rendering of the backlog - // can take some time. The value of 33ms means that we wait for 1 whole frame at 30 fps, which - // should be more than enough. - bool gotLock = entriesLock.try_lock_for(33ms); + // can take some time, especially during heavy load like compiling shaders. + bool gotLock = entriesLock.try_lock_for(100ms); if (gotLock) { entries.push_back(entry);