From ade765d6bd164449ee460261176d2734d85cd41c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6nke=20Ludwig?= Date: Tue, 15 Dec 2020 19:43:20 +0100 Subject: [PATCH] Fix a worker task scheduling issue for busy worker tasks. Fixes new tasks being able to be scheduled on a worker thread while a busy task (that periodically calls yield()) is running. --- source/vibe/core/taskpool.d | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/source/vibe/core/taskpool.d b/source/vibe/core/taskpool.d index ebf3816..ff56aba 100644 --- a/source/vibe/core/taskpool.d +++ b/source/vibe/core/taskpool.d @@ -346,7 +346,16 @@ private final class WorkerThread : Thread { try { if (m_pool.m_state.lock.term) return; logDebug("entering worker thread"); - handleWorkerTasks(); + + // There is an issue where a task that periodically calls yield() + // but otherwise only performs a CPU computation will cause a + // call to runEventLoopOnce() or yield() called from the global + // thread context to not return before the task is finished. For + // this reason we start a task here, which in turn is scheduled + // properly together with such a task, and also is schduled + // according to the task priorities. + runTask(&handleWorkerTasks).joinUninterruptible(); + logDebug("Worker thread exit."); } catch (Throwable th) { th.logException!(LogLevel.fatal)("Worker thread terminated due to uncaught error");